webpack-dev-server vulnerable to cross-origin WebSocket access via proxied upgrades
Résumé
webpack-dev-server is a development server that provides live reloading for webpack projects. In versions before 5.2.7 and in version 6.0.0, when a proxy entry is configured to forward WebSockets, the server forwards non-HMR WebSocket upgrade requests to the proxy target without validating the Host...
Résumé IA
Rédigé par une IA externe ; il peut contenir des erreurs. Vérifiez la description d'origine et les références ci-dessous avant d'agir.
webpack-dev-serverの一部の版では、プロキシ設定でWebSocketを転送する場合に、HostやOriginの検証が行われません。悪意のあるWebページを開発者が閲覧すると、開発サーバー経由で接続先のバックエンドの情報を読み書きされるおそれがあります。影響を受けるのは5.2.7未満と6.0.0で、5.2.7と6.1.0以降に更新してください。
Paquets affectés
| Écosystème | Paquet | Concernées | Corrigé |
|---|---|---|---|
| webpack-dev-server | webpack-dev-server |
< 5.2.7 ≥ 6.0.0, < 6.1.0 |
5.2.7 6.1.0 |
Description d'origine La description telle que publiée par la source (souvent en anglais).
webpack-dev-server is a development server that provides live reloading for webpack projects. In versions before 5.2.7 and in version 6.0.0, when a proxy entry is configured to forward WebSockets, the server forwards non-HMR WebSocket upgrade requests to the proxy target without validating the Host or Origin headers, so the allowedHosts protection does not apply to those proxied upgrades. A malicious web page visited by a developer can open a cross-origin WebSocket through the dev server and read from and write to the proxied backend, even when the server is bound to loopback. The issue is fixed in webpack-dev-server 5.2.7 and 6.1.0, where proxied WebSocket upgrades pass the same Host and Origin validation as the HMR WebSocket, and users should upgrade to one of those versions or later. As a workaround, omit WebSocket forwarding from proxy entries that do not need it and scope the proxy to specific paths.
Source: CVE.org (CVE Program・cvelistV5) NVD
Références
- web github.com
- web cna.openjsf.org