Added a section to the blog post explaining it in broad strokes:
## tl;dr * 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. * 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. On Mon, May 7, 2012 at 11:14 AM, Ben Noordhuis <i...@bnoordhuis.nl> wrote: > On Mon, May 7, 2012 at 7:34 PM, Marco Rogers <marco.rog...@gmail.com> wrote: >> I'm assuming this affects 0.4.x as well. > > No, this only applies to v0.6. > > v0.4 probably has its own share of defects but this one is not part of that. > :-) -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
