Denial of Service in http-proxy-agent
Summary
GHSA-8w57-jfpm-945m: Denial of Service in http-proxy-agent. Affects http-proxy-agent versions < 2.1.0. Fixed in 2.1.0. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The http-proxy-agent package is an npm package that provides an HTTP proxy agent implementation for use with the http and https modules. It allows users to make HTTP requests through a proxy server. The package is widely used in various Node.js applications.
Vulnerability Detail
Versions of http-proxy-agent before 2.1.0 are vulnerable to a denial of service (DoS) attack and uninitialized memory leak when unsanitized options are passed to Buffer. This vulnerability can be exploited by an attacker to consume system resources, leading to a DoS condition. The issue originates from the lack of proper sanitization of user-supplied input, allowing malicious actors to trigger the vulnerability.
How To Fix
Minimum fixed version
2.1.0
This is the first release that contains the fix.
npm install http-proxy-agent@2.1.0
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no known workaround for this vulnerability. It is essential to update to the fixed version of the package to mitigate the risk.
Conclusion
In conclusion, the http-proxy-agent package versions prior to 2.1.0 are vulnerable to a denial of service attack and uninitialized memory leak. It is crucial to update to the fixed version of the package (2.1.0 or later) to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for http-proxy-agent →
FAQ
This vulnerability can be exploited by an attacker to consume system resources, leading to a denial of service condition. It may result in the unavailability of the affected application or system.
You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities using package-lock.json without requiring access to the code or installation.
There are no known workarounds for this vulnerability. It is crucial to update to the fixed version of the package to mitigate the risk.
The recommended solution is to update to version 2.1.0 or later of the http-proxy-agent package. Updating to the latest version will ensure that the necessary security patches are applied.
You can find more information about this vulnerability in the GitHub Security Advisory database at https://github.com/github/advisory-database/advisories/GHSA-8w57-jfpm-945m.
References
Related vulnerabilities
Recent vulnerabilities recorded for http-proxy-agent.