CVE-2016-3956
HIGHCVSS 7.5/10EPSS 6.75%
Last modified
CVE-2016-3956 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. The CLI in npm before 2.15.1 and 3.x before 3.8.3, as used in Node.js 0.10 before 0.10.44, 0.12 before 0.12.13, 4 before 4.4.2, and 5 before 5.10.0, includes bearer tokens with arbitrary requests, which allows remote HTTP servers to obtain sensitive information by reading Authorization headers.. EPSS estimates a 6.75% chance of exploitation in the next 30 days.
Description
The CLI in npm before 2.15.1 and 3.x before 3.8.3, as used in Node.js 0.10 before 0.10.44, 0.12 before 0.12.13, 4 before 4.4.2, and 5 before 5.10.0, includes bearer tokens with arbitrary requests, which allows remote HTTP servers to obtain sensitive information by reading Authorization headers.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Ibm | Sdk | <= 1.1.0.20 | — |
| Ibm | Sdk | <= 1.2.0.10 | — |
| Ibm | Sdk | <= 4.4.1.0 | — |
| Nodejs | Node.Js | 0.10.0 | — |
| Nodejs | Node.Js | 0.10.1 | — |
| Nodejs | Node.Js | 0.10.2 | — |
| Nodejs | Node.Js | 0.10.3 | — |
| Nodejs | Node.Js | 0.10.4 | — |
| Nodejs | Node.Js | 0.10.5 | — |
| Nodejs | Node.Js | 0.10.6 | — |
| Nodejs | Node.Js | 0.10.7 | — |
| Nodejs | Node.Js | 0.10.8 | — |
| Nodejs | Node.Js | 0.10.9 | — |
| Nodejs | Node.Js | 0.10.10 | — |
| Nodejs | Node.Js | 0.10.11 | — |
| Nodejs | Node.Js | 0.10.12 | — |
| Nodejs | Node.Js | 0.10.13 | — |
| Nodejs | Node.Js | 0.10.14 | — |
| Nodejs | Node.Js | 0.10.15 | — |
| Nodejs | Node.Js | 0.10.16 | — |
| Nodejs | Node.Js | 0.10.16-isaacs-manual | — |
| Nodejs | Node.Js | 0.10.17 | — |
| Nodejs | Node.Js | 0.10.18 | — |
| Nodejs | Node.Js | 0.10.19 | — |
| Nodejs | Node.Js | 0.10.20 | — |
| Nodejs | Node.Js | 0.10.21 | — |
| Nodejs | Node.Js | 0.10.22 | — |
| Nodejs | Node.Js | 0.10.23 | — |
| Nodejs | Node.Js | 0.10.24 | — |
| Nodejs | Node.Js | 0.10.25 | — |
| Nodejs | Node.Js | 0.10.26 | — |
| Nodejs | Node.Js | 0.10.27 | — |
| Nodejs | Node.Js | 0.10.28 | — |
| Nodejs | Node.Js | 0.10.29 | — |
| Nodejs | Node.Js | 0.10.30 | — |
| Nodejs | Node.Js | 0.10.31 | — |
| Nodejs | Node.Js | 0.10.32 | — |
| Nodejs | Node.Js | 0.10.33 | — |
| Nodejs | Node.Js | 0.10.34 | — |
| Nodejs | Node.Js | 0.10.35 | — |
| Nodejs | Node.Js | 0.10.36 | — |
| Nodejs | Node.Js | 0.10.37 | — |
| Nodejs | Node.Js | 0.10.38 | — |
| Nodejs | Node.Js | 0.10.39 | — |
| Nodejs | Node.Js | 0.10.40 | — |
| Nodejs | Node.Js | 0.10.41 | — |
| Nodejs | Node.Js | 0.12.0 | — |
| Nodejs | Node.Js | 0.12.1 | — |
| Nodejs | Node.Js | 0.12.2 | — |
| Nodejs | Node.Js | 0.12.3 | — |
Showing 50 of 89 affected configurations. See NVD for the full list.
References
- http://www-01.ibm.com/support/docview.wss?uid=swg21980827Vendor Advisory
- https://github.com/npm/npm/commit/f67ecad59e99a03e5aad8e93cd1a086ae087cb29Patch, Third Party Advisory
- https://github.com/npm/npm/commit/fea8cc92cee02c720b58f95f14d315507ccad401Patch, Third Party Advisory
- https://github.com/npm/npm/issues/8380Third Party Advisory
- http://www-01.ibm.com/support/docview.wss?uid=swg21980827Vendor Advisory
- https://github.com/npm/npm/commit/f67ecad59e99a03e5aad8e93cd1a086ae087cb29Patch, Third Party Advisory
- https://github.com/npm/npm/commit/fea8cc92cee02c720b58f95f14d315507ccad401Patch, Third Party Advisory
- https://github.com/npm/npm/issues/8380Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-3956?
The CLI in npm before 2.15.1 and 3.x before 3.8.3, as used in Node.js 0.10 before 0.10.44, 0.12 before 0.12.13, 4 before 4.4.2, and 5 before 5.10.0, includes bearer tokens with arbitrary requests, which allows remote HTTP servers to obtain sensitive information by reading Authorization headers.
How severe is CVE-2016-3956?
CVE-2016-3956 has a CVSS score of 7.5/10 (HIGH severity). The EPSS model estimates a 6.75% probability of exploitation in the next 30 days.
How do I fix CVE-2016-3956?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2016
- CVE-2016-3950Huawei AR3200 routers with software before V200R006C10SPC300…
- CVE-2016-3951Double free vulnerability in drivers/net/usb/cdc_ncm.c in th…
- CVE-2016-3952web2py before 2.14.1, when using the standalone version, all…
- CVE-2016-3953The sample web application in web2py before 2.14.2 might all…
- CVE-2016-3954web2py before 2.14.2 allows remote attackers to obtain the s…
- CVE-2016-3955The usbip_recv_xbuff function in drivers/usb/usbip/usbip_com…9.8
- CVE-2016-3957The secure_load function in gluon/utils.py in web2py before …
- CVE-2016-3958Untrusted search path vulnerability in Go before 1.5.4 and 1…7.8
- CVE-2016-3959The Verify function in crypto/dsa/dsa.go in Go before 1.5.4 …
- CVE-2016-3960Integer overflow in the x86 shadow pagetable code in Xen all…
- CVE-2016-3961Xen and the Linux kernel through 4.5.x do not properly suppr…
- CVE-2016-3962Stack-based buffer overflow in the NTP time-server interface…
Are you affected by CVE-2016-3956?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST