Skip to content

GHSA-86wf-436m-h424 CVE-2019-10196

Resource Exhaustion Denial of Service in http-proxy-agent

Critical npm
Severity
9.8 / 10
Critical · CVSS 3.1
Exploit chance (EPSS)
1.39%
Chance of exploitation in the next 30 days. Higher than 72.35% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-665 Improper Initialization
Fix
2.1.0
Upgrade http-proxy-agent to this version or later

Description

A flaw was found in http-proxy-agent, prior to version 2.1.0. It was discovered http-proxy-agent passes an auth option to the Buffer constructor without proper sanitization. This could result in a Denial of Service through the usage of all available CPU resources and data exposure through an uninitialized memory leak in setups where an attacker could submit typed input to the auth parameter.

Affected versions

npm

PackageVulnerableFixed in
http-proxy-agent
< 2.1.0
2.1.0

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

http-proxy-agent npm → 2.1.0

npm
npm install http-proxy-agent@2.1.0
yarn
yarn add http-proxy-agent@2.1.0
pnpm
pnpm add http-proxy-agent@2.1.0

Severity breakdown

CVSS 3.1 9.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-665: Improper Initialization

The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used.

How to prevent it
  • Requirements: Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, in Java, if the programmer does not explicitly initialize a variable, then the code could produce a compile-time error (if the variable is local) or automatically initialize the variable to the default value for the variable's type. In Perl, if explicit initialization is not performed, then a default value of undef is assigned, which is interpreted as 0, false, or an equivalent value depending on the context in which the variable is accessed.
  • Architecture and Design: Identify all variables and data stores that receive information from external sources, and apply input validation to make sure that they are only initialized to expected values.
  • Implementation: Explicitly initialize all your variables and other data stores, either during declaration or just before the first usage.
  • Implementation: Pay close attention to complex conditionals that affect initialization, since some conditions might not perform the initialization.
  • Implementation: Avoid race conditions (CWE-362) during initialization routines.
  • Build and Compilation: Run or compile your product with settings that generate warnings about uninitialized variables or data.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-8w57-jfpm-945m
Denial of Service in http-proxy-agent
High Also affects http-proxy-agent
GHSA-cmwh-pvxp-8882
DOMPurify: Permanent `ALLOWED_ATTR` pollution via `setConfig()` bypassing the hook clone-guard (incomplete fix of the 3.4.7 hook-pollution patch)
Medium Same weakness, CWE-665
GHSA-2fqr-mr3j-6wp8
aiohttp: Host-Only Cookies Become Domain Cookies After CookieJar Persistence
High Same weakness, CWE-665
GHSA-7rrj-xr53-82p7
Tokio reject_remote_clients configuration may get dropped when creating a Windows named pipe
Medium Same weakness, CWE-665
GHSA-v2cv-wwxq-qq97
Moby Docker cp broken with debian containers
Critical Same weakness, CWE-665
CVE-2022-0847
A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe and push_pipe…
High Known exploited Same weakness, CWE-665
GHSA-pw3c-h7wp-cvhx
Improper Initialization in Pillow
Medium Same weakness, CWE-665
GHSA-9c22-pwxw-p6hx
Improper Initialization in OpenZeppelin
Medium Same weakness, CWE-665
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor