Denial of Service in http-proxy

published 2020-09-04 6y ago modified 2024-01-29 2y ago

cvss: 7.5; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

Versions of `http-proxy` prior to 1.18.1 are vulnerable to Denial of Service. An HTTP request with a long body triggers an `ERR_HTTP_HEADERS_SENT` unhandled exception that crashes the proxy server. This is only possible when the proxy server sets headers in the proxy request using the `proxyReq.setHeader` function.

For a proxy server running on `http://localhost:3000`, the following curl request triggers the unhandled exception: ```curl -XPOST http://localhost:3000 -d "$(python -c 'print("x"*1025)')"```

## Recommendation

Upgrade to version 1.18.1 or later

Patch / fix

fixed in 1 links 2

npm http-proxy 1.18.1

github.com/http-party/node-http-proxy#1447 commit
github.com/http-party/node-http-proxy#1447 pull request

Is GHSA-6x33-pw7p-hmpq in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem	package	affected	fixed in
npm	http-proxy	<1.18.1	1.18.1

Classification

Weakness

CWE-184 Incomplete List of Disallowed Inputs
CWE-693 Protection Mechanism Failure

References

Sources

GitHub Advisory GHSA-6x33-pw7p-hmpq

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.