Re:Vulnerability in HTTP.sys Could Allow Remote Code Execution
by ComputerGuru on Tuesday April 14, 2015 @11:28PM
(#9378748)
The details of CVE-2015-1635 seem to still be undisclosed, but given that it's an HTTP praying issue I wonder if running IIS behind nginx or another reverse proxy (a very common configuration) would help any? It's not listed under mitigating factors, but maybe that's really less of a mitigating factor and more of a "doesn't apply" situation?
[ Parent
| on HN ]
Re:Vulnerability in HTTP.sys Could Allow Remote Code Execution
by MichaelGG on Wednesday April 15, 2015 @02:57AM
(#9379293)
It might be. Depends on how well nginx or another frontend will sanitize or parse things. Another link says it's a range header issue. So if nginx doesn't handle line folding, but HTTP.SYS does, you might still sneak it by. HTTP is a clusterfuck to parse.
Anyways I doubt MS would write "Mitigating factor: Not using IIS."
Also note, this does not just apply to IIS. It applies to the Windows kernel HTTP stack (?!), HTTP.SYS. Which is used by many things apart from IIS. And can even be listening when your app is not running (OS opens a socket on port 80, 443, whatever, runs it as SYSTEM (PID 4), then passes the HTTP messages off to your app if your app is up and connected.)