CVE-2018-3739 json
Denial of Service in https-proxy-agent
published 8y ago modified last mo. also GHSA-8g7p-74h8-hg48 , EUVD-2018-0249
- cvss
- 9.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
https-proxy-agent before 2.1.1 passes auth option to the Buffer constructor without proper sanitization, resulting in DoS and uninitialized memory leak in setups where an attacker could submit typed input to the 'auth' parameter (e.g. JSON).
Patch / fix
- npm https-proxy-agent 2.2.0
- https-proxy-agent_project https-proxy-agent 2.2.0
Is CVE-2018-3739 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 FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2018-3739 updated cvss 8.2
nodejs-https-proxy-agent: Unsanitized options passed to Buffer() allow for denial of service
-
Red Hat Quay 3 quay/quay-rhel8affected: no fix available “Fix deferred”
-
Red Hat Software Collections rh-nodejs8-npm, rh-nodejs8-nodejsaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 8 npm, nodejs, nodejs-libs, nodejs-nodemon, nodejs-full-i18n, nodejs-packaging, +1 more Red Hat Mobile Application Platform 4 nodejs-https-proxy-agent Red Hat Software Collections rh-nodejs10-npm, rh-nodejs10-nodejsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.74% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- hackerone.com https://hackerone.com/reports/319532 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H |
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:P/I:N/A:P |
| GitHub | 3.0 | 9.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | https-proxy-agent | <2.2.0 |
2.2.0 |
Affected products
- HackerOne https-proxy-agent node module
Classification
References
-
github.com
/TooTallNate/node-https-proxy-agent/commit/1c24219df87524e6ed973127e81f30801d658f07
web
-
hackerone.com
/reports/319532
web, exploit, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-3736
advisory
-
github.com
/TooTallNate/node-https-proxy-agent
package
-
github.com
/advisories/GHSA-8g7p-74h8-hg48
advisory
-
npmjs.com
/advisories/593
web
Sources
- CVE List CVE-2018-3739
- GitHub Advisory GHSA-8g7p-74h8-hg48
- NVD CVE-2018-3739
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.