Slashdot Log In
Vista Protected Processes Bypassed
Posted by
CowboyNeal
on Sat Apr 07, 2007 11:41 AM
from the falling-confidence-levels dept.
from the falling-confidence-levels dept.
Anonymous Hero writes "Security Researcher Alex Ionescu strikes again, this time with a proof of concept program that will arbitrarily enable and foremost disable the protection of so-called 'protected processes' in Windows Vista. Not only threatening Vista DRM and friends, it's also another step towards hardened and even more annoying malware. Normally, only specially signed processes made by special companies (decided by Microsoft) can be protected, but now the bad guys can protect any evil process they want, including the latest version of their own keylogger, spambot, or worm, as well as unprotect any 'good' one."
Related Stories
[+]
Vista DRM Cracked by Security Researcher 379 comments
An anonymous reader writes "Security researcher Alex Ionescu claims to have successfully bypassed the much discussed DRM protection in Windows Vista, called 'Protected Media Path' (PMP), which is designed to seriously degrade the playback quality of any video and audio running on systems with hardware components not explicitly approved by Microsoft. The bypass of the DRM protection was in turn performed by breaking the Driver Signing / PatchGuard protection in the new operating system. Alex is now quite nervous about what an army of lawyers backed by draconian copyright laws could do to him if he released the details, but he claims to be currently looking into the details of safely releasing his details about this at the moment though."
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
In related news (Score:5, Funny)
Re:In related news (Score:5, Insightful)
A spokesperson for Microsoft was quoted as saying :
This is only an issue if you're downloading and watching porn. You should be watching only wholesome media, like "What About Bob", instead.
People are modding this as flamebait, but I've seen far, FAR too many IT professionals take that stance with Spyware / Malware. I've seen a system get all sorts of nasty winlogon-enabled Spyware within minutes of being hooked up to a network, with no action on the user's part. Not only that, in a world where banner ad companies can get infected with trojans [out-law.com] the idea of people only getting infected if they're doing something "shady" on their machine is utterly absurd.
Parent
Re:In related news (Score:4, Informative)
It was a joke, just a joke and only a joke.
The link given is to Microsoft Bob, which Microsoft gave up on shortly after launching it and (according to Wikipedia) later admitted the product was their single largest failure in their company history.
You'd need to remember Bob in order to appreciate that Vista is well on its way to being "Bob 2".
I suppose any joke could be taken as flamebait lol, but really, its just a joke. Better put in
its funny, laugh.
Parent
Re:In related news (Score:5, Interesting)
Vista goes way ot of its way to reduce functionality for the user in order to make content providers happy. Think of what that really means. Company A sells something to Consumer A but that something is disabled in order to make Company B happy. Company B is happy because they can continue their old business model and maintain their dominance if and when they finally move into new business models when they feel ready. Meanwhile, companies C, D and E through M move to create, innovate and design new things only to be prevented by both Company A and Company B. Depending on how this is done and how much evidence can be produced, this is illegal behavior.
Parent
Re: (Score:3, Insightful)
Re:In related news (Score:5, Interesting)
The parent is not necessarily too uptight to admit surfing porn.
Parent
Re:In related news (Score:5, Funny)
Parent
Re:In related news (Score:4, Insightful)
Do a significant proportion of porn sites have malware? Probably.
Is there a greater risk of getting infected by malware when surfing for porn than doing "wholesome" surfing? Perhaps.
Is a malware infection reason enough to presume that they got it from browsing porn and/or piracy-related sites? Not in the slightest in my experience. If you've got differing experiences that prove me wrong, by all means collate your data and present your findings because I and I'm sure many other people working in admin or IT roles would love some hard numbers on the nature of malware sources online. Until then I'll have to assume the "observations of thousands of admins" you speak of are in fact nothing more than your own pre-conceptions.
Parent
Re: (Score:3, Interesting)
I'll tell you, personally I think porn sites don't need malware. They KNOW what you're there for - they don't need to slap adware on your system to get you to come there. I've always had some spyware protection back when I was running mostly on Windows 2000 and XP, and I surfed porn sites frequently (albeit with Opera originally and later Firefox, more than IE, so my exposure to ActiveX was minimal) and I very rarely got any spyware according to my utilities.
Basically ANY sleazy commercial outfit will slap
Didn't we see this before... (Score:3, Informative)
I clearly remember being called to help a friend with a spyware/malware problem, discoverng he had ME, and going out to buy a copy of XP to replace it.
Re:Didn't we see this before... (Score:5, Funny)
Parent
this is just an another step (Score:4, Funny)
Wait, wait... (Score:5, Interesting)
Most likely I am missing the point here, and can't understand TFA accordingly. Somebody please set me straight.
Re:Wait, wait... (Score:4, Informative)
It's not like they can just create a pointer and address the other memory space but using the API they can achieve the same thing.
This is what allows programs like xfire to inject into your game process or (as they mention in TFA) allows Warden to peek inside all processes to see if they are evil.
Parent
No, debuggers can't have special privileges (Score:3, Interesting)
When you make a Windows API call to something like CreateRemoteThread [microsoft.com], you need a handle to the process you're interested in. If the right security bits aren't set (and they get set by the call to CreateProcess), CreateRemoteThread returns unsuccessfully.
Anyway, what could you do to give debuggers special privilege
Re: (Score:3, Interesting)
Ever since DOS (Score:5, Insightful)
Re:Ever since DOS (Score:5, Funny)
I miss the days when I gave my computer commands not suggestions.
You are becoming nostalgic, Deny or Allow?
Parent
It's really Melinda's fault (Score:5, Funny)
So get off your old, tired, 20th Century horse and get with the new paradigm.
Just a suggestion of course.
Parent
Re:Ever since DOS (Score:4, Funny)
Parent
biting the hand that feeds you (Score:5, Funny)
He [Alex Ionescu] is also a Microsoft Student Ambassador and is representing the company on campus as a Technical Rep.
not for long, I bet.
New Meaning for "Genuine Advantage" (Score:3, Funny)
possible silver lining (Score:4, Interesting)
Surprising really? (Score:4, Funny)
Again? (Score:3, Interesting)
Bill Gates wants more cheap labor [infoworld.com] to waste of useless software [theinquirer.net]. What a waste of human intellect and talent. How about making the computer RUN faster, be more intuitive, and reliable?
Good, now MS cant dictate software advantage (Score:4, Insightful)
by doing that they give incumbents an advantage over others and are using their OS to exapand monopoly interests into other sectors.
Good idea, bad implementation. (Score:5, Insightful)
"Protected processes" are a reasonable idea. They're certainly better than putting video and audio processing in the kernel as part of the DRM system. But apparently Microsoft botched the implementation.
Microsoft has for some years allowed processes to do too much to other processes. Things like "injecting" a DLL or thread into a running process from the outside, or "hooking" system calls, are inherently security problems. In the Windows world, normal processes can do that to each other. This tends to be overdone, with too much "hooking" of system calls and such, a tradition from the DOS era. The UNIX/Linux world doesn't have that tradition. Fortunately.
In the Linux world, the things you can't do to a Microsoft "protected process" are roughly equivalent to the functions of the PTRACE [linuxgazette.net] call. In SElinux, the mandatory security system controls which processes can use PTRACE on which other processes. [12.110.110.204] So SELinux already has "protected processes", but with a better security model.
If we have to have DRM, protected processes aren't a bad idea. But what you want is for them to be compartmented, not privileged. They should be running in a compartment which prevents other processes from attaching to them, but they don't need the privilege of attaching to other processes. So the video decoder can be protected, but doesn't have enough privileges to act as an aimbot for some game. The security system for a game should be able to lock the game processes into a compartment which other processes cannot enter, preventing cheats. Enforce separation, not privilege.
Re:Good idea, bad implementation. (Score:4, Informative)
Parent
This is how it's done (Score:5, Informative)
The Philosophy of Protection (Score:4, Insightful)
So what do you do? Well, one thing you don't do is provide special security rights to only certain approved software.
The only true answer is open software and education. People who don't know how to use their computers will be attacked. They will be compromised. If you can't control yourself on the internet and local networks, you will lose the right to control your computer because someone will take it from you. If you run unknown and untrusted programs, you face the risks. Your online habits help determine your exposure. If you absolutely must visit 'free porn', warez, social networks like MySpace, etc websites, then do so with caution tempered by proper education on how to isolate your important, sensitive data, from the rest of the crap you are willing to lose. You are better off simply not visiting sites of that nature. But if you are going to, at least understand how to keep yourself safe. Because no software written today is going to be able to do it for you. There will always be software out there capable of getting around it.
In the end, to the wolves go the slowest, weakest sheep. It's natural. Don't be one of them.
Looks like 32-bit (Score:4, Interesting)
32-bit allows unsigned code in kernel mode for legacy reasons so its much more easier to inject into 32-bit processes.
Re:Other OSes (Score:4, Funny)
Parent
Re:Other OSes (Score:5, Insightful)
Parent
Re:Other OSes (Score:5, Informative)
Parent
Re:Can't beat em, join em? (Score:5, Insightful)
Parent
You think so? (Score:3, Insightful)
Re:You think so? (Score:4, Funny)
Parent
Re:Can't beat em, join em? (Score:4, Insightful)
-matthew
Parent
Re:Can't beat em, join em? (Score:4, Funny)
Why would anyone bother putting in more backdoors to the OS equivalent of Goatse ?
Parent
Re:Can't beat em, join em? (Score:4, Interesting)
That's MS's big problem. A LOT of people WANT them to fail because they're MS. Because fundamentally, a computer and it's OS is supposed to do what the user wants, not what Bill Gates, the RIAA and the MPAA want it to do. There are enough people out there who know how to hack it up so it actually does do what they want. The more pragmatic ones WANT MS to fail because that's how to crack the content they want.
Once the hacking is accomplished, a significant number of people will then abuse that code to get other people's computers to do what THEY want rather than what Bill wants (doing what the user wants is simply not up for discussion).
The real beauty here is that the "bad guys" are turning the OS's own features against the creator (the other bad guys). The divine appropriatness of that is simply irresistable.
Parent
Re:Why do they even bother? (Score:5, Insightful)
Parent
Re:Why do they even bother? (Score:5, Funny)
Parent
Re:Why do they even bother? (Score:5, Insightful)
The problem with Microsoft is not so much one of bugs as it is a problem with their general design philosophy.
Such as providing mechanisms for your own developers to bypass the security of the entire system to make some friggin media clips play more smoothly. News flash, idiots: if you provide two paths through security, a strongly checked path and a weakly checked path, you incentivize attackers to take the weak path! And if you provide those hooks for your own developers to bypass security, then attackers can use them too!
They were probably praying that no one would ever figure out that those hooks were there... and security by obscurity is very, very poor design.
My inclinations against myself or my family running vista just got a +1 Justification.
Parent
Re: (Score:3, Insightful)
Microsoft needs to be put out of business. Now. They have all the brains and social conscience of Enron.
Re:DRM in Vista is misunderstood (Score:5, Insightful)
Parent
You're joking, right? (Score:3, Informative)
The ability to play some DRM'd files was also added to XP and Windows 2000. I assume you already knew that though...
Re: (Score:3, Insightful)
> Why can XP and Windows 2000 play encrypted files?
The ability to play some DRM'd files was also added to XP and Windows 2000. I assume you already knew that though...
Ok so your original quote that suggested Vista's DRM, which is clearly different when compared to XP's and 2000's DRM mechanisms, is somehow a good thing was wrong? Or were you trying to say that some type of DRM is necessary? If the latter, then I don't know yet if I disagree. I can't however understand why you would criticize Ionescu for enlightening us to the flaws in Vista's security/DRM strategy. Ionescu did not make Vista any less secure than it was a week ago. He's simply let some of us know tha
Re: (Score:3, Funny)
Re:Source code (Score:5, Insightful)
Parent
Re:Source code (Score:4, Informative)
Seems to contain a compressed buffer with a .sys driver that is decompressed with a call to RtlDecompressBuffer and hidden away by writing it to the alternate stream "%SystemRoot%\system32\drivers\crusoe.sys:drmkaud. sys", and then there's a registry update to load the driver.
Someone who cares should write out the compressed buffer and disassemble that.
Parent