A request smuggling vulnerability was found in Node.js that can be exploited under certain
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.
@maintainer(s): after the bump, in case we need to stabilize the package, please let us know if it is ready for the stabilization or not.
Update from maintainer (by proxy):
One of these vulnerabilities actually lives in net-libs/http-parser which was bumped to 2.6.1 Yesterday.
net-libs/nodejs-5.6.0 is work in progress; an ebuild sent for review (to proxies) available here: https://github.com/gentoo/gentoo/pull/781
"Unfortunately" we also have to bump 0.10, 0.12, and the LTS 4.x series. I will be reviewing these ebuilds the coming days. http-parser might not be releasing stable series for each of these so I will have to review that it works as intended before we bump.
If anyone wants more information about these vulnerabilities, feel free to contact me privately.
ebuild for both http-parser-2.6.1 and nodejs-5.6.0 are in tree.
Does 4.4.1 fix this? (it should be stabilized in bug 568900 it seems)
please test and mark stable: =net-libs/nodejs-0.12.10
Maintainer(s), please cleanup.
Security, please vote.
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.
Node.js 0.10.x before 0.10.42, 0.12.x before 0.12.10, 4.x before 4.3.0, and
5.x before 5.6.0 allow remote attackers to conduct HTTP request smuggling
attacks via a crafted Content-Length HTTP header.
Proxy-maint package... tree is clean:
GLSA Vote: No