5 ms·

ASCII NUL is indeed 0x0. http://en.m.wikipedia.org/wiki/Null_character http://en.m.wikipedia.org/wiki/Null_character http://www.bibase.com/images/ascii.gif htt

• masklinn 12y ago
  But '0' is not ascii NUL (0x00), it's ascii 0 (0x30).
  • eis 12y ago
    Additionally there are a bunch of other things very wrong with the exploit code. If the connect() fails, it will use file descriptor 1 which is usually stdout and write the request to it and try to read from it. And there is a problem with strstr() not getting a null terminated string (if the stack memory for recvBuff wasn't automatically zero'd out which some compilers can do). Why do these people bother writing the exploit in C? A curl one liner is good enough. Also the check for 'The request has an invalid header name' seems dubious to me because a proxy in front would likely return a different error (the header name is not invalid but rather the range not satisfyable).
• ehmmm 12y ago
  '0' != '\0' '0' == 48
  • benjamincburns 12y ago
    I wasn't suggesting anything to the contrary...
    • ehmmm 12y ago
      Yes, but there also isn't any NULs in the parent. So you can understand the confusion.
• deleted 12y ago
  [deleted]