News for hackers. Stuff that matters.
Re:Vulnerability in HTTP.sys Could Allow Remote Code Execution by nbevans on Tuesday April 14, 2015 @11:05PM (#9378681)
It's a bad time for the C programming language. First OpenSSL. Then SQLite this week. Now HTTP.sys. They didn't move HTTP into the kernel as a driver lightly; it was done on the assumption the code would be vetted and tested throughly. Clearly that has failed.
Re:Vulnerability in HTTP.sys Could Allow Remote Code Execution by higherpurpose on Wednesday April 15, 2015 @01:08AM (#9378987)
By OpenSSL are you referring to HeartBleed? Windows has already had a similarly serious (let's call it) "bug" that allowed remote execution in IIS servers. Except unlike Heartbleed which only existed for 2 years, Microsoft's bug was in Windows for 20 years.

But since Microsoft (on purpose) didn't make a unique name and logo for it, the media didn't pick it up. They gave it an obscure name and made it part of a larger Windows update, where they also added a few other "security improvements", which the media actually reported on more than on the bug.

Some were calling it "WinShock" if you want to Google (or Bing) for it.

Re:Vulnerability in HTTP.sys Could Allow Remote Code Execution by gtirloni on Wednesday April 15, 2015 @06:42AM (#9380011)
Interesting that if you don't make a show out of a bug, you're doing it "on purpose". I assume you didn't mean to generalize but the current practice of naming bugs, making logos and what not is just silly.
Re:Vulnerability in HTTP.sys Could Allow Remote Code Execution by nbevans on Wednesday April 15, 2015 @12:48PM (#9382266)
"But since Microsoft (on purpose) didn't make a unique name and logo for it, the media didn't pick it up."

Haha! I don't think MS got that memo about having to name bugs and make logos.

Re:Vulnerability in HTTP.sys Could Allow Remote Code Execution by MichaelGG on Tuesday April 14, 2015 @11:13PM (#9378704)
Not so fast. We don't know if this is actually a memory safety issue. It be some sort of non-memory logic error.
Re:Vulnerability in HTTP.sys Could Allow Remote Code Execution by UnoriginalGuy on Tuesday April 14, 2015 @11:23PM (#9378735)
A non-memory logic error that allows remote code execution by breaking the stack? Can you give an example? Most of the examples I can think of are either directly or indirectly a problem of memory safety (for execution remote code rather than simply crashing (like a stack overflow)).
Re:Vulnerability in HTTP.sys Could Allow Remote Code Execution by MichaelGG on Wednesday April 15, 2015 @12:06AM (#9378827)
I don't see any details about breaking the stack (just the HTTP stack). Maybe you can request arbitrary ranges of files and they get cached in a way that lets you reference them as ISAPI filters. I'm grasping at straws but I'm not feeling particularly creative right now.

I was also being slightly sarcastic. I'd take the bet this is a memory safety issue, but there's a chance it isn't.

Re:Vulnerability in HTTP.sys Could Allow Remote Code Execution by 0x0 on Wednesday April 15, 2015 @03:04AM (#9379316)
How about that old WMF vulnerability? :)