Google Researchers Find Wormable 'Crazy Bad' Windows Exploit (bleepingcomputer.com)
An anonymous reader quotes a report from BleepingComputer: Two Google security experts have found a severe remote code execution (RCE) bug in the Windows OS, which they've described as "crazy bad." The two experts are Natalie Silvanovich and Tavis Ormandy, both working for Project Zero, a Google initiative for discovering and helping patch zero-days in third-party software products. The two didn't release in-depth details about the vulnerability, but only posted a few cryptic tweets regarding the issue. Drilled with questions by the Twitter's infosec community, Ormandy later revealed more details: the attacker and the victim don't necessarily need to be on the same LAN; the attack works on a default Windows install, meaning victims don't need to install extra software on their systems to become vulnerable; the attack is wormable (can self-replicate). The tweets came days before Microsoft's May 2017 Patch Tuesday, scheduled tomorrow, May 9. The researchers said a report is coming, alluding the vulnerability might be patched this month, and they'll be free to publish their findings.
Can we post some equally-bad Linux vulns please? Intel, Microsoft, they can't be the only ones having all the fun.
It is pitch black. You are likely to be eaten by a grue.
Are you telling me Windows isn't secure? Windows called me and said my PC had malware and only charges me $666 per month to keep it clean.
And installed debian instead of windows..
"File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
I'll bet it's some service that's running by default and listening on a port. Probably SMB or some crap they've created in the name of convenience.
See this alternate link http://securityaffairs.co/word...
Here you go, it's an oldie, but goodie.... https://en.wikipedia.org/wiki/...
Given the number of abandonware Linux devices in the field... I'm sure this one is still alive and kicking, though...
Arm the WSUS servers!
I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
crazy bad ... experts ... the attack is wormable (can self-replicate)
Which is it then, RCE exploit or some kind of malware? Sounds like bullshit.
Official announcement: https://technet.microsoft.com/en-us/library/security/4022344
More background / report: https://bugs.chromium.org/p/project-zero/issues/detail?id=1252&desc=5
tl;dr: The Javascript engine in Windows Defender (which tries to figure out if it's a virus) has a flaw. Exploit works and can be leveraged if you can force the victim to write something to disk (triggering a scan): eg, sending an email, viewing an image, writing a log entry, etc.
Not a Windows Update, the fix is coming as part of the Windows Defender definitions updates rollout process.
Hire a Linux system administrator, systems engineer,
Apparently, it seems that they are provoking certain part of Windows Defender (which is triggered automatically by virtually any action on the target computer) to take a wrong input which it cannot gracefully manage. By quoting the aforementioned report:
Nscript supports "short" strings, with length and values contained in the handle and "long" strings with out-of-line memory. If the string is "long" (or appears to be due to type confusion), a vtable call is made to retrieve the length.
As I understand it, this isn't precisely an ideal situation although seems to belong to the kind of software-crashing-because-of-not-adequately-managing-all-scenarios problems. An assumption which seems to be confirmed in that same report when they say:
The attached proof of concept demonstrates this, but please be aware that downloading it will immediately crash MsMpEng in it's default configuration and possibly destabilize your system.
So, how is this weak point expected to be truly exploited? Are they only planning to provoke Windows Defender in random machines to crash and, eventually, the system to become unstable? This should certainly be looked at, but is it a real threat? Another part of this report seems to clarify this point further:
Integer handles are represented as four-byte values with the final bit set to one by the engine. The integer itself is left shifted by one bit, and the final bit set to create the handle. Handles to most objects, including strings are represented as the value of the pointer to the object with no modification. Therefore, this type confusion allows an integer to be specified and treated as pointer (though the bits need to shifted to get the correct value in the handle, and only odd pointer values are possible).
Are they implying that the only way of this attack to perform any action on the target computer (other than crashing Windows Defender) is to guess how a pointer might look like (by bearing in mind that they have to perform some bit-shifting actions and that only half of all the possible scenarios can be considered!)??!! How such a thing could ever by accomplished under absolutely any circumstance? Guessing the pointers of the objects in a (very complex) code from an external machine? This is orders of magnitude more complicated (actually, it can be considered plainly impossible) than exploiting a problem which I analysed in an old version of CoreRun.exe (used to test open-source modifications in one of the most basic .NET libraries) and my conclusion back then was that it wasn’t a threat! (Although Microsoft did modify this part a short time later; not sure if because of my public analysis, nobody said never anything to me. Anyone interested in all this can take a look at Project 8 in varocarbas.com).
This situation can also be described by using a perhaps-clearer-for-a-wider-audience SQL injection analogy: by assuming that you can access a database because its inputs aren't adequately sanitised (refer to the famous Little Bobby Tables study), you would need to know where to look at (e.g., table or column names), an action which is relatively easy when dealing with the most logical configuration of almost any database. But now imagine that you are accessing a database where the names of all the entities are randomly assigned and you have no way to know about their current values; in that scenario, how would accessing that database via injection be useful at all? Should the inputs be adequately sanitised and each single step should be done properly just in case and because developing properly-built-at-each-poi
Custom Solvers 2.0 = Alvaro Carballo Garcia = varocarbas.
MS have already pushed a fix for this out; everything should magically auto-update to fix the vulnerability.
More details here.
Good job by all. Responsible disclosure plus super fast response time.
For those not aware the vulnerability has already been patched as part of KB4016240 which is already been pushed out on windows update. The details of the issue are fully disclosed.
Any and all content posted above may be ignored, considered irrelevant, or otherwise dismissed.
Remote exploit that can replicate is bad, very, very bad. The Sapphire worm reached exponential growth and infected 90% of vulnerable systems in 10 minutes. It was a single UDP packet (no timeouts, handshakes, etc.) but some research I did a decade ago proved that, at least theoretical, a TCP-based worm can perform in the same order of magnitude.
Not much has happened in this area recently, mostly because the bad guys have shifted to spam, botnets and ransomware. With the IoT, there's a lot of fun just around the corner.
Assorted stuff I do sometimes: Lemuria.org
I'm going to guess that it has to do with Windows Update. A service that always runs, randomly consumes all CPU and RAM, and loves to talk on the network. It's as bad as a botnet. Please, oh please, tell me it is Windows Update.
Either that or a TCP/IP or UDP/IP "malformed" packet issue. I put malformed in quotes because maybe it's the NSA backdoor that everyone's been looking for since Windows NT 4.
You see, there are CVE Levels Of Bad:
1). Not Bad
2). Not Too Bad
3). Bad-ish
4). Bad
5). Very Bad
6). Really Bad
7). Mega Bad
8). Crazy Bad
9). Batshit Bad
10). systemd Bad
11). Narco-Terrorists in Your Livingroom Bad!
The scale goes to 11 because, you know, that's one more than the highest on most scales.