Microsoft To Issue Emergency IE Patch 79
CWmike writes "Microsoft will release its emergency patch for Internet Explorer on Thursday, the company said, as it also admitted that attacks can be hidden inside rigged Office documents. 'We are planning to release the update as close to 10:00 a.m. PST as possible,' said Jerry Bryant, a program manager with the IE group. Microsoft has updated the security advisory it originally published last week when it acknowledged a zero-day IE vulnerability had been used by hackers to break into the corporate networks of Google and other major Western companies. Google has alleged that the attacks were launched by Chinese attackers. Subsequently, security experts have offered evidence that links the attacks to China."
Attack targeted perforce repositories? (Score:3, Insightful)
Reat that the attack targeted Perforce repositories. Haven't heard if any other source control systems were targeted.
Pretty clever way to gather intellectual property; I'd never considered it before, but for many companies if you can download their repository data then you have their crown jewels.
Define Emergency (Score:2, Insightful)
Shows difference between IT and politics (Score:5, Insightful)
It's not really news that lots of exploits could (and probably were) abused for espionage (both corporate and international). But only now that 'teh evil chinese' are happily hacking along some action is taken.
This is exactly the kind of problem that could be avoided by listening to security experts.
Thanks M$ for giving a crap about the security of users, companies and countries... You're a few years too late stepping up the game, but please keep it up, we might as well have security as an afterthought instead of no security at all.
Comment removed (Score:4, Insightful)
Re:While I welcome the patch.... (Score:2, Insightful)
I wish MS would make a version of IE that ran in the popular Linux distros without emulation, then I could use it and be vulnerable as well.
Re:Yikes (Score:5, Insightful)
Looks like a basic architectural problem. Or else it would nor persist as long, trough so many changes.
No need to bash MS on top of the usual, because Win7 still has it. Think of a basic core library that just works since back then and does not need changing. You overlooked something, and someone found a way that you did no think about.
That’s normal, an can happen to anyone.
It’s usually not the bugs that are the problem. Everything has bugs.
It’s the way MS handles fixing them. With massive denial, attacking others for mentioning it, and then a very very late, half-assed patch that needs another patch to patch the patch.
That’s the real problem.
Would MS just have a normal bugzilla, and in the normal case quickly fix the important bugs, I would have no problem with that. Mozilla does it just like that. And even Mozilla has a couple of long-standing bugs. I guess every big software has them. Because every software has a base architecture that you can only re-build every so many years in the complete rewrite. So bugs that don require that architecture to change can’t simply be fixed.
Oh, that reminds me, that for IE, that rewrite is long overdue. That’s the reason there are so many big bugs in there. But I don’t see MS doing a complete rewrite, unless they are forced to completely throw away the old Trident engine.
Affected software list (Score:3, Insightful)
http://www.computerworld.com/s/article/9145958/Researchers_up_ante_create_exploits_for_IE7_IE8?taxonomyId=17&pageNumber=2
Essentially, if you're using back versions of the operating system and don't keep updated, you're vulnerable. What makes this exploit different from a lot of others is that it has such a large attack surface. However, from what I'm gathering, the default Windows 7 install with IE8 should be safe from any attacks. As soon as you start disabling technologies (UAC, DEP)--you will run into problems.
Re:stolen source (Score:4, Insightful)
Re:stolen source (Score:3, Insightful)
It merely shows yet another weak point in closed source development model -- if the code is leaked or given to bad guys, they can thoroughly analyze and exploit it while good guys can't do anything about it -- they have no legal means to obtain and analyze the code.
Open source development model does not, of course, have such issues with source code in the wild. Black hats can look at the code in both cases, but open development model is better because it easily allows white hats to have a good look too.
Yet another example that security through obscurity won't work, nothing really new here.
Re:stolen source (Score:3, Insightful)