Re:Remote Kernel Code Execution Via HTTP Request In IIS On W...
by masklinn on Wednesday April 15, 2015 @09:21AM
(#9380751)
But '0' is not ascii NUL (0x00), it's ascii 0 (0x30).
Re:Remote Kernel Code Execution Via HTTP Request In IIS On W...
by eis on Wednesday April 15, 2015 @09:31AM
(#9380811)
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).
Re:Remote Kernel Code Execution Via HTTP Request In IIS On W...
by ehmmm on Wednesday April 15, 2015 @09:23AM
(#9380766)
'0' != '\0'
'0' == 48
Re:Remote Kernel Code Execution Via HTTP Request In IIS On W...
by benjamincburns on Thursday April 16, 2015 @05:03AM
(#9386701)
I wasn't suggesting anything to the contrary...
http://en.m.wikipedia.org/wiki/Null_character http://www.bibase.com/images/ascii.gif