Microsoft warns: Expect exploits for critical Windows worm hole
Summary: There's a remote, pre-authentication, network-accessible code execution vulnerability in Microsoft's implementation of the RDP protocol.
Attention Microsoft Windows administrators: Stop what you're doing and apply the new -- and very critical -- MS12-020 update.
Microsoft is warning that there's a remote, pre-authentication, network-accessible code execution vulnerability in its implementation of the RDP protocol.
From the bulletin:
A remote code execution vulnerability exists in the way that the Remote Desktop Protocol accesses an object in memory that has been improperly initialized or has been deleted. An attacker who successfully exploited this vulnerability could run abitrary code on the target system. An attacker could then install programs; view,change, or delete data; or create new accounts with full user rights.
The vulnerability, which affects all versions of Windows, was privately reported to Microsoft's via the ZDI vulnerability broker service and the company said it was not yet aware of any attacks in the wild.
Although RDP is disabled by default, Microsoft is urging all Window users to treat this issue with the utmost priority.
"Due to the attractiveness of this vulnerability to attackers, we anticipate that an exploit for code execution will be developed in the next 30 days," Microsoft said.
It's important to note that the vulnerable code is reachable only if RDP is enabled and a mitigation feature in RDP called NLA (network level authentication) moves it to post-authentication which makes this vulnerability less likely to be wormed. There are instructions here to enable NLA on Windows to reduce the severity of a potential attack.
[ SEE: Ten little things to secure your online presence ]
The Remote Assistance feature in Windows (see image above) provides checkboxes for users to choose between “more secure” and “less secure”. On machines where RDP is enabled in the “less secure" mode, nothing blocks pre-auth code execution once a stable exploit is developed.This issue is potentially reachable over the network by an attacker before authentication is required. RDP is commonly allowed through firewalls due to its utility. The service runs in kernel-mode as SYSTEM by default on nearly all platforms (except for one exception described below). During our investigation, we determined that this vulnerability is directly exploitable for code execution. Developing a working exploit will not be trivial – we would be surprised to see one developed in the next few days. However, we expect to see working exploit code developed within the next 30 days.
In all, Microsoft shipped six security bulletins as part of this month's Patch Tuesday batch. The updates address seven documented vulnerabilities in Microsoft Windows, Visual Studio and Expression Design.
Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback
Microsoft warns: Expect exploits for critical Windows worm hole
Sure, those MCSEs aren't known for having this port open
Its been a while since we've had a solid windows worm.
Give it a rest.
Mcitp
And a good mcitp will make sure the patch provided today will get applied to all those servers AND all of the clients they might administer/support.
So are most of the ABMers arguments.
I though Loverock davidson was the only solid windows worm........
Ye, surprisingly it may as well be 2003
sjaak327 says the MCSE will patch today without testing, going through change control, informing users of an outage and preparing an impact statement? What am I saying of course they will, then click reboot (whilst crossing fingers).
Many corporate servers will have RDP exposed on the LAN to a number of users just waiting for one to open something to begin an attack from within (happens all the time).
Hard to compete with the skills and experience of the NBMers;-)
I agree!
Given your inability to come up with an original argument since then.
2003 the blaster worm
It attacked a patched vulnerability.
Yep, I feel like I'm back in 2003.
Already submitted to change control
RDP is disabled on all desktop systems company wide via GPO already so no issue there. We'll let that patch roll out via normal WSUS testing and deployment.
But you're right, this will still hit some people and people like you will blame MS. There's not much they can do besides provide patches. A responsible IT department is already working on this. A lot of them aren't responsible. And it doesn't matter what "certs" they have, I've found incompetent Linux admins. They are more rare as Linux is more difficult to use. But it does happen.
Doesn't count anyway.
MCSEs haven't got any better
I agree. Like changing the cert name and updating it will end the same kind of mistakes they made back in 2003?
Puh-leaseee...
lol...
that's right officer barbrady nothing to see here...
@TG2 is correct
Errrr. Think again.
Then you have some who aren't on the latest supported service pack for threir OS. I know of someone a while back who noticed that he wasn't getting any security updates. At one point, when asked, he didn't want to install SP2 for Vista.
Got the alerts on my WSUS server
Wondering.....
RE: Wondering
Servers are a different story and I am very selective on what I update on those.
Microsoft's Critcal Fixes