DoS and memory disclosure via unsafe Buffer construction
Published Mar 19, 2021 · Updated Aug 4, 2024
Improper initialization in TooTallNate http-proxy-agent before 2.1.0 allows remote attackers to exhaust CPU and expose memory via crafted auth input. The callback in index.js passed proxy.auth directly to the deprecated new Buffer constructor, which could allocate from attacker-controlled typed values and return uninitialized bytes. Exploitation requires a consuming application to accept attacker-controlled auth data; impact is service interruption and indirect disclosure of process memory.
Summary
What happened
Improper initialization in TooTallNate http-proxy-agent before 2.1.0 allows remote attackers to exhaust CPU and expose memory via crafted auth input. The callback in index.js passed proxy.auth directly to the deprecated new Buffer constructor, which could allocate from attacker-controlled typed values and return uninitialized bytes. Exploitation requires a consuming application to accept attacker-controlled auth data; impact is service interruption and indirect disclosure of process memory.
The record
- CVE
- CVE-2019-10196
- Published
- Mar 19, 2021
- Updated
- Aug 4, 2024
- Vendor
- TooTallNate
- Product
- http-proxy-agent
- Classifications
- CWE-665, T1499, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 19, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=prior to nodejs-http-proxy-agent 2.1.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo