I tried to send the bad curl request to our servers (test env, obviously) and I didn't get any error. It seems I should be getting "Requested Range Not Satisfiable" if the server is vulnerable and "The request has an invalid header name" if it's patched. I'm getting neither, simply a normal response HTTP 200 with the requested page. Anyone knows how to really test it? EDIT : It is indeed related to "Output Cache" set…
Remote Kernel Code Execution Via HTTP Request In IIS On Windows
131–140 of 201 posts
Re: Remote Kernel Code Execution Via HTTP Request In IIS On Windows
#132But wait, I thought Micro$oft were lauded as having "got" security these days? Surely it is isn't so!
Lets not play the "my team is better than your team" hysterics, especially when we all had to do emergency patching for shellshock, heartbleed, samba, etc in the past couple months. Hell, sambra runs as root too. There's a lot of security stupidity out there. I'm still waiting for a unixy OS to be written in something like Rust.
Re: Remote Kernel Code Execution Via HTTP Request In IIS On Windows
#133Earlier quoted context omitted.
I fully agree that the idea doesn't make sense, specially when coupled with memory unsafe languages. Just wanted to make the point it isn't a Windows specific idea.
Deploying this sort of thing in production on the other hand seems to be a Windows specific idea.
I'm kind of surprised this issue wasn't discovered previously. Fortunately, there doesn't seem to be an exploit beyond crashing the server yet (which is bad enough). (sigh, kind of glad I'm in the process of migrating everything away from IIS).
Re: Remote Kernel Code Execution Via HTTP Request In IIS On Windows
#134I tried to send the bad curl request to our servers (test env, obviously) and I didn't get any error. It seems I should be getting "Requested Range Not Satisfiable" if the server is vulnerable and "The request has an invalid header name" if it's patched. I'm getting neither, simply a normal response HTTP 200 with the requested page. Anyone knows how to really test it? EDIT : It is indeed related to "Output Cache" set…
I just crashed a 2008 R2 server without a rule, just with "Enable Kernel Caching". Not sure if it is relevant, but I first added a rule for .png, and then removed it again. Still worked.
If you can't afford to reboot your servers right now to install the patch, at least you can add this to your web.config and deploy your websites ASAP :
Re: Remote Kernel Code Execution Via HTTP Request In IIS On Windows
#135The interesting take-away is the .sys suffix on the filename: Yes, Windows contains a device driver running in Kernel mode that cares about (IIS) HTTP traffic.
Windows also has a TCP/IP stack in the kernel. And a GUI stack (win32k.sys).
Re: Remote Kernel Code Execution Via HTTP Request In IIS On Windows
#136Isn't a lot of government using IIS? How long before someone starts attacking their services with this? Is Azure vulnerable?
Re: Remote Kernel Code Execution Via HTTP Request In IIS On Windows
#137I tried to send the bad curl request to our servers (test env, obviously) and I didn't get any error. It seems I should be getting "Requested Range Not Satisfiable" if the server is vulnerable and "The request has an invalid header name" if it's patched. I'm getting neither, simply a normal response HTTP 200 with the requested page. Anyone knows how to really test it? EDIT : It is indeed related to "Output Cache" set…
I installed the pending windows updates and after a restart the problem seems to be gone.
Re: Remote Kernel Code Execution Via HTTP Request In IIS On Windows
#138But does it have a catchy name yet? I suggest: Long-range
Re: Remote Kernel Code Execution Via HTTP Request In IIS On Windows
#139I tried to send the bad curl request to our servers (test env, obviously) and I didn't get any error. It seems I should be getting "Requested Range Not Satisfiable" if the server is vulnerable and "The request has an invalid header name" if it's patched. I'm getting neither, simply a normal response HTTP 200 with the requested page. Anyone knows how to really test it? EDIT : It is indeed related to "Output Cache" set…
Re: Remote Kernel Code Execution Via HTTP Request In IIS On Windows
#140Earlier quoted context omitted.
Sounds like the author understands the bug but does not understand why it allows remote code execution (which I don't understand either; once details are released it should be clarified).
That's a good point, because in the example we can clearly see how to check if a system is or not patched and that, using this attack, we can crash a Windows Server. The remote execution part is completely missing (fortunately), but I was wondering if this gives the admin rights on machine (I have absolutely no experience on Windows Server machines, so I don't know how it works in terms of services, permissions and r…
The heap spraying is the missing puzzle piece from the article.