First published: Sat Oct 19 2024(Updated: )
http-proxy-middleware is vulnerable to a denial of service, caused by an UnhandledPromiseRejection error thrown by micromatch. By sending specially crafted requests to certain paths, a remote attacker could exploit this vulnerability to kill the Node.js process and crash the server.
Credit: report@snyk.io report@snyk.io
Affected Software | Affected Version | How to fix |
---|---|---|
npm/http-proxy-middleware | >=3.0.0<3.0.3 | 3.0.3 |
npm/http-proxy-middleware | <2.0.7 | 2.0.7 |
http-proxy-middleware | <2.0.7 | |
http-proxy-middleware | >=3.0.0<3.0.3 |
https://github.com/chimurai/http-proxy-middleware/commit/0b4274e8cc9e9a2c5a06f35fbf456ccfcebc55a5
https://github.com/chimurai/http-proxy-middleware/commit/788b21e4aff38332d6319557d4a5b1b13b1f9a22
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-21536 is categorized as a denial of service vulnerability due to unhandled promise rejections in http-proxy-middleware.
To fix CVE-2024-21536, update http-proxy-middleware to version 3.0.3 or later, or to 2.0.7 if using an earlier version.
CVE-2024-21536 affects http-proxy-middleware versions from 3.0.0 to 3.0.2 and versions before 2.0.7.
An attacker can exploit CVE-2024-21536 by sending specially crafted requests, which may crash the Node.js server.
More information about CVE-2024-21536 can typically be found in security advisories and vulnerability databases.