re-posting here: A carefully crafted attack request can cause the contents of the HTTP parser’s buffer to be appended to the attacking request’s header, making it appear to come from the attacker. Since it is generally safe to echo back contents of a request, this can allow an attacker to get an otherwise correctly designed server to divulge information about other requests. It is theoretically possible that it could enable header-spoofing attacks, though such an attack has not been demonstrated. Versions affected: All versions of the 0.5/0.6 branch prior to 0.6.17, and all versions of the 0.7 branch prior to 0.7.8. Versions in the 0.4 branch are not affected. Fix: Upgrade to v0.6.17, or apply the fix in c9a231d to your system. We have: 0.6.15 and 0.7.8. I can confirm that bumping to 0.6.17 works nicely on my setups (already changed in production after confirming in staging)
0.6.17 added, 0.7.8 already there, vulnerable versions punted.
*** Bug 415103 has been marked as a duplicate of this bug. ***
Package was never stable, closing noglsa.
CVE-2012-2330 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-2330): The Update method in src/node_http_parser.cc in Node.js before 0.6.17 and 0.7 before 0.7.8 does not properly check the length of a string, which allows remote attackers to obtain sensitive information (request header contents) and possibly spoof HTTP headers via a zero length string.
