Exploit Wednesday follows MS Patch Tuesday
Summary: Less than 24 hours after Microsoft shipped fixes for code execution holes in Internet Explorer and Windows, proof-of-concepts for remote exploits are popping up on the Internet.
Less than 24 hours after Microsoft shipped fixes for code execution holes in Internet Explorer and Windows, proof-of-concepts for remote exploits are popping up on the Internet.
On security mailings lists and at the Milw0rm.com site, there are at least three exploits circulating. These provide a roadmap for attackers to launch remote attacks to take complete control of an Windows machine.
Two of the three target gaping holes in the dominant Internet Explorer browser -- flaws that could be exploited by simply luring the target to surf to a Web page. (See exploit code here and here).
The vulnerabilities -- in the Microsoft Speech API ActiveListen and ActiveVoice ActiveX controls -- have been patched with the MS07-033 bulletin so it's important to treat that update with the highest possible priority. * [ SEE: ‘Critical’ Vista, IE 7 patches highlight MS security updates ]
Will Dorman of the CERT Coordination Center explains the real-world risks:
By convincing a user to view a specially crafted HTML document (e.g., a web page or an HTML email message or attachment), an attacker may be able to execute arbitrary code with the privileges of the user. The attacker could also cause Internet Explorer (or the program using the WebBrowser control) to crash.
This patch applies to Internet Explorer 7 on Windows Vista.
Proof-of-concept code for a third exploit was released by Thomas Lim of COSEINC to provide technical details of of a "critical" flaw in the Secure Channel (Schannel) security package in Windows. This bug was patched with MS07-031.
* See step-by-step instructions on configuring Internet Explorer to run securely in our image gallery.
Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.
Talkback
Here we go again !?!?!?!?
P.S. This goes out to Shelendrea
A patch for a patch that was suppose to fix the problem in the first place .
See my post.
Having the problems in the first place, no comment. Vista more/less secure, no comment, maybe in 6 months to a year (certainly more secure than previous Windows). ActiveX should die, I agree completely. javascript should die, agree completely. Both enable ease of use, and are just really really crappy in terms of security.
TripleII
You keep saying that
Carl Rapson
Here you go
http://talkback.zdnet.com/5208-12691-0.html?forumID=1&threadID=31710&messageID=585291&start=9
TripleII
Nice!
Danske Tripell for saving my *ss this time .
Swiss cheese
Dunno about "explicitly"...
http://www.betanews.com/article/Microsoft_Vista_Most_Secure_OS_Ever/1150366131
Which starts off by saying: "Microsoft senior vice president Bob Muglia opened up TechEd 2006 in Boston Sunday evening by proclaiming that Windows Vista was the most secure operating system in the industry."
This article seems to be found in several places via google using advanced search for '"Bob Muglia" TechEd 2006' as the criteria.
So I started looking for the keynote and found this:
http://teched06.blogspot.com/
Which, down in the text, points to some video of the keynote. I can't seem to get to the site.
So did he or didn't he? I wasn't there to report.
He did .
PSSST.....
Gotcha
ROTFL
BTW- I believe it was more along the lines of the patch that patch the patch that patched the patch that was supposed to patch the patch from last month =-)
On another note..... I did think that Vista WAS supposed to be more secure.
Also (and this goes for any OS, product, platform... take your pick) when they patch something (ie FIX it) theoretically there shouldn't be a way to get through it.
Why do you gloat so?
Rock and a hard place
I want to put kudo's out there to MS for patching, working to make things more secure for the user, but I do want to ask the experts here, what, really is critical in ActiveX that it couldn't be done in .net, or java, or some other way?
In the history of patches, and infections, how much can be attributed back to ActiveX.
TripleII
Again, javascript is no better and probably worse in terms of the current security model.
Microsoft needs ActiveX to destroy Java...
Performance
Performance. ActiveX controls are compiled, binary code, meaning that it runs with as fast of performance as possible. Contrast that with Java or .NET which are compiled at runtime.
I can't imagine Flash, especially when decoding and playing video, getting decent performance if it was written as a Java applet or .NET plugin. ActiveX is the way to go.
P.S. These aren't bugs in IE or in its ActiveX support. These are bugs in the actual ActiveX controls (COM objects) themselves (the speech/ActiveVoice objects). IE is the primary attack vector, but other ones exist, for example a Microsoft Word document that uses the object.
ActiveX not inherently (much) more dangerous than Java
Examples are the dozens of IE exploits over the years that allowed drive-by installs of activex controls, and the confusing installation confirmation interface (A simple box with uninformative text and yes/no buttons) in early versions of IE.
Since ActiveX controls are installed globally, and can do anything that any other program can do, they rightly require admin rights to install. But that never mattered one bit since Microsoft gave admin rights by default in XP.
I think the problem with ActiveX came down to it being so damn easy to install controls. It's already super easy to install new software on Windows. ActiveX + IE made it so that instead of having to download and executable, and run it (which some newbie computer users have trouble doing) all you had to do was click one button.
The sort of havoc caused by ActiveX controls can by caused with Java applets too, so I wouldn't be so quick to proclaim Java (or .NET or whatever else) as the savior.
I remember a thread in a security forum (dslreports.com) started by someone who used Opera exclusively and somehow got infected with nasty spyware while browsing the web. This person was shocked and wanted to know how he could have been infected. It turned out he was running a slightly outdated versions of Suns JRE, which was affected by multiple vulnerabilities that allowed remote code execution, and/or "drive-by installs".
Thanks for the info
TripleII
Don't forget the rules!
1. User level exploit (on Vista).
2. PoC only.
3. Requires user intervention.
4. Already patched.
Vista...100% unscathed so far.
Ye you are in denial .