Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

21
  • 130
    P.S: This answer is from the person who originally discovered the bug :) Commented Sep 25, 2014 at 15:02
  • 6
    @Ben Isn't that the answer to the opposite question? Commented Sep 26, 2014 at 18:00
  • 33
    May I ask… did you stumble upon the bug serendipitously, or were you actively looking for bugs in Bash? Commented Sep 26, 2014 at 20:01
  • 7
    @gerrit Because the bug doesn't cause any bad behavior under normal conditions. Since nothing goes wrong nobody's looking at the code other than security researchers and black hats. Commented Sep 27, 2014 at 3:51
  • 4
    @JacekSzymanski true, but what about other headers? especially custom headers? (an attacker can just add an X-Exploit-Payload header that should be set as HTTP_X_EXPORT_PAYLOAD) Commented Sep 29, 2014 at 8:38