CVE-2016-2216
published 2016-04-07CVE-2016-2216: The HTTP header parsing code in Node.js 0.10.x before 0.10.42, 0.11.6 through 0.11.16, 0.12.x before 0.12.10, 4.x before 4.3.0, and 5.x before 5.6.0 allows…
PriorityP349high7.5CVSS 3.0
AVNACLPRNUINSUCNIHAN
EPSS
7.01%
93.4th percentile
The HTTP header parsing code in Node.js 0.10.x before 0.10.42, 0.11.6 through 0.11.16, 0.12.x before 0.12.10, 4.x before 4.3.0, and 5.x before 5.6.0 allows remote attackers to bypass an HTTP response-splitting protection mechanism via UTF-8 encoded Unicode characters in the HTTP header, as demonstrated by %c4%8d%c4%8a.
Affected
91 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| apple | xcode | — | — |
| debian | nodejs | < nodejs 4.3.0~dfsg-1 (bookworm) | nodejs 4.3.0~dfsg-1 (bookworm) |
| fedoraproject | fedora | — | — |
| fedoraproject | fedora | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
CVSS provenance
nvdv3.07.5HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:N/I:P/A:N
osv7.5HIGH
vendor_debian7.5LOW
vendor_redhat7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-77qx-hwx7-xv2g: The HTTP header parsing code in Node
ghsa_unreviewed·2022-05-17
CVE-2016-2216 [HIGH] CWE-20 GHSA-77qx-hwx7-xv2g: The HTTP header parsing code in Node
The HTTP header parsing code in Node.js 0.10.x before 0.10.42, 0.11.6 through 0.11.16, 0.12.x before 0.12.10, 4.x before 4.3.0, and 5.x before 5.6.0 allows remote attackers to bypass an HTTP response-splitting protection mechanism via UTF-8 encoded Unicode characters in the HTTP header, as demonstrated by %c4%8d%c4%8a.
OSV
CVE-2016-2216: The HTTP header parsing code in Node
osv·2016-04-07·CVSS 7.5
CVE-2016-2216 [HIGH] CVE-2016-2216: The HTTP header parsing code in Node
The HTTP header parsing code in Node.js 0.10.x before 0.10.42, 0.11.6 through 0.11.16, 0.12.x before 0.12.10, 4.x before 4.3.0, and 5.x before 5.6.0 allows remote attackers to bypass an HTTP response-splitting protection mechanism via UTF-8 encoded Unicode characters in the HTTP header, as demonstrated by %c4%8d%c4%8a.
Apple
CVE-2016-2216: Xcode 8.1
vendor_apple·2016-10-27·CVSS 7.5
CVE-2016-2216 [HIGH] CVE-2016-2216: Xcode 8.1
Apple Security Update: About the security content of Xcode 8.1
Product: Xcode
Version: 8.1
CVE: CVE-2016-2216
Component: CVE-2016-2216
Red Hat
nodejs: Response splitting vulnerability using Unicode characters
vendor_redhat·2016-02-09·CVSS 7.5
CVE-2016-2216 [HIGH] CWE-113 nodejs: Response splitting vulnerability using Unicode characters
nodejs: Response splitting vulnerability using Unicode characters
The HTTP header parsing code in Node.js 0.10.x before 0.10.42, 0.11.6 through 0.11.16, 0.12.x before 0.12.10, 4.x before 4.3.0, and 5.x before 5.6.0 allows remote attackers to bypass an HTTP response-splitting protection mechanism via UTF-8 encoded Unicode characters in the HTTP header, as demonstrated by %c4%8d%c4%8a.
It was found that nodejs functions manipulating HTTP headers did not properly forbid invalid characters. An attacker with ability to tamper with HTTP headers could use this flaw to inject a new-line allowing a response splitting attack.
Package: nodejs010-nodejs (Red Hat OpenShift Enterprise 2) - Will not fix
Package: nodejs (Red Hat OpenShift Enterprise 3) - Not affected
Package: nodejs010-nodejs (Red Ha
Debian
CVE-2016-2216: nodejs - The HTTP header parsing code in Node.js 0.10.x before 0.10.42, 0.11.6 through 0....
vendor_debian·2016·CVSS 7.5
CVE-2016-2216 [HIGH] CVE-2016-2216: nodejs - The HTTP header parsing code in Node.js 0.10.x before 0.10.42, 0.11.6 through 0....
The HTTP header parsing code in Node.js 0.10.x before 0.10.42, 0.11.6 through 0.11.16, 0.12.x before 0.12.10, 4.x before 4.3.0, and 5.x before 5.6.0 allows remote attackers to bypass an HTTP response-splitting protection mechanism via UTF-8 encoded Unicode characters in the HTTP header, as demonstrated by %c4%8d%c4%8a.
Scope: local
bookworm: resolved (fixed in 4.3.0~dfsg-1)
bullseye: resolved (fixed in 4.3.0~dfsg-1)
forky: resolved (fixed in 4.3.0~dfsg-1)
sid: resolved (fixed in 4.3.0~dfsg-1)
trixie: resolved (fixed in 4.3.0~dfsg-1)
No detection rules found.
No public exploits indexed.
HackerOne
Multiple HTTP Smuggling reports
hackerone·2019-11-12·CVSS 9.8
[CRITICAL] Multiple HTTP Smuggling reports
Multiple HTTP Smuggling reports
Theses reports spreads other several years and are all about **HTTP Smuggling issues**
(HTTP Requests or Responses splitting, Cache Poisoning, Security filter bypass).
I've made reports on a wide range of open source projects, explaining
the (not always easy) problems to the various security maintainers and testing the fixs.
The starting point for this work was the 2005 work published by Amit Klein and some others:
* 2004 - Amit Klein : "Divide and Conquer: HTTP Response Splitting, Web Cache Poisoning Attacks, and Related Topics" https://packetstormsecurity.com/papers/general/whitepaper_httpresponse.pdf
* 2005 - Chaim Linhart, Amit Klein, Ronen Heled, Steve Orrin: "HTTP Request Smuggling" https://www.cgisecurity.com/lib/HTTP-Request-Smuggling.pdf
* 2006 -
Bugzilla
CVE-2016-2216 nodejs: Response splitting vulnerability using Unicode characters
bugzilla·2016-02-10·CVSS 7.5
CVE-2016-2216 [HIGH] CVE-2016-2216 nodejs: Response splitting vulnerability using Unicode characters
CVE-2016-2216 nodejs: Response splitting vulnerability using Unicode characters
It was reported that HTTP header parsing in Node.js is vulnerable to response splitting attacks. While Node.js has been protecting against response splitting attacks by checking for CRLF characters, it is possible to compose response headers using Unicode characters that decompose to these characters, bypassing the checks previously in place.
External Reference:
https://nodejs.org/en/blog/vulnerability/february-2016-security-releases/
Discussion:
Created nodejs tracking bugs for this issue:
Affects: fedora-all [bug 1306207]
Affects: epel-all [bug 1306208]
---
Root cause analysis:
http://blog.safebreach.com/2016/02/09/http-response-splitting-in-node-js-root-cause-analysis/
---
nodejs-0.10.42-4.fc23 ha
Bugzilla
CVE-2016-2216 CVE-2016-2086 nodejs: various flaws [epel-all]
bugzilla·2016-02-10·CVSS 7.5
CVE-2016-2216 [HIGH] CVE-2016-2216 CVE-2016-2086 nodejs: various flaws [epel-all]
CVE-2016-2216 CVE-2016-2086 nodejs: various flaws [epel-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora EPEL.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora EPEL.
Bugzilla
CVE-2016-2216 CVE-2016-2086 nodejs: various flaws [fedora-all]
bugzilla·2016-02-10·CVSS 7.5
CVE-2016-2216 [HIGH] CVE-2016-2216 CVE-2016-2086 nodejs: various flaws [fedora-all]
CVE-2016-2216 CVE-2016-2086 nodejs: various flaws [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora. While o
http://blog.safebreach.com/2016/02/09/http-response-splitting-in-node-js-root-cause-analysis/http://info.safebreach.com/hubfs/Node-js-Response-Splitting.pdfhttp://lists.fedoraproject.org/pipermail/package-announce/2016-February/177184.htmlhttp://lists.fedoraproject.org/pipermail/package-announce/2016-February/177673.htmlhttp://packetstormsecurity.com/files/135711/Node.js-HTTP-Response-Splitting.htmlhttp://www.securityfocus.com/bid/83141https://nodejs.org/en/blog/vulnerability/february-2016-security-releases/https://security.gentoo.org/glsa/201612-43http://blog.safebreach.com/2016/02/09/http-response-splitting-in-node-js-root-cause-analysis/http://info.safebreach.com/hubfs/Node-js-Response-Splitting.pdfhttp://lists.fedoraproject.org/pipermail/package-announce/2016-February/177184.htmlhttp://lists.fedoraproject.org/pipermail/package-announce/2016-February/177673.htmlhttp://packetstormsecurity.com/files/135711/Node.js-HTTP-Response-Splitting.htmlhttp://www.securityfocus.com/bid/83141https://nodejs.org/en/blog/vulnerability/february-2016-security-releases/https://security.gentoo.org/glsa/201612-43
2016-04-07
Published