Hacker Claims Ability to Exploit Windows Update

CommanderFrank

Cat Can't Scratch It
Joined
May 9, 2000
Messages
75,399
The hacker who stole the digital certificates from a Dutch firm claims that he could use them to issue fake Microsoft Updates. The fake updates could be used to introduce malware through the Windows Update download servers.

Among the 531 certificates stolen in the hack of Dutch-based DigiNotar were several that could be used to impersonate Microsoft's update services.
 
I'd like to see that asshole try. Microsoft has their Update service locked up tighter than Fort Knox.
 
All if his certificates have been invalidated. No browser, excecpt safari will accept them.
Microsoft also pulled any accpetance of the certs from windows itself, which if I read correctly from another site, is the same place IE gets its info from.
 
If he could have done it I think he would have while he had the chance instead of blogging about it. Plus it doesn't even seem that these certificates even had any authorization to use Windows Update.
 
Seems like a ploy to get people to NOT update and patch security holes in their system, because they think it might be a hacker. If you can get the gullible masses to turn off auto-update it would be great for malware makers.
 
well that didn't last long...

WRONG.. if you mean the hacker didn't get away with it for very long as, unfortunately, he did. The following is quoting Steve Gibson on his "Security Now" podcast (episode 317) from Sept 8 reading a statement from Mozilla..

STEVE: Yeah. So Mozilla, following up, said, "Earlier this week we revoked our trust in the DigiNotar certificate authority from all Mozilla software." Now, that's different from what we discussed last week, where, as I said, they made sort of a surgical, we're going to suspend trust in the following certificates, which we know have been compromised. Now they're saying, get a new copy of Mozilla stuff, we're pulling the plug. They said, "This is not a temporary suspension. This is a complete removal from our trusted root program. Complete revocation of trust is a decision we treat with careful consideration and employ as a last resort. Three central issues informed our decision:

"One: Failure to notify. DigiNotar detected and revoked some of the fraudulent certificates six weeks ago without notifying Mozilla. This is particularly troubling since some of the certificates were issued for our own addons.mozilla.org domain.

"Two: The scope of the breach remains unknown. While we were initially informed by Google that a fraudulent *.google.com certificate had been issued, DigiNotar eventually confirmed that more than 200 certificates had been issued against more than 20 different domains." Of course now we know it's way more than that. So, and this says, "We now know that the attackers also issued certificates from another of DigiNotar's intermediate certificates without proper logging. It is therefore impossible for us to know how many fraudulent certificates exist, or which sites are targeted.

Can find the podcast audio and/or transcript at http://www.grc.com/securitynow.htm

128970342624121974.jpg
 
  • Like
Reactions: Santa
like this
WRONG.. if you mean the hacker didn't get away with it for very long as, unfortunately, he did. The following is quoting Steve Gibson on his "Security Now" podcast (episode 317) from Sept 8 reading a statement from Mozilla..

Perhaps you understand better than I or most but what do any of these certs have to do with Windows Update?
 
I seriously doubt it as I understand the certs have been blocked on the kernel level.
 
These certificates have been blocked at an OS level in both Windows and OS X, as well as complete revocation from every Firefox version 3.6 and up. This twat can't do anything with them anymore. Every certificate Diginotar has ever issued, even the legitimate ones have now been banned from pretty much 98% of the web traffic out there.

I haven't heard anything about a revocation of certificates regarding the various Linux Distros, but I'm sure it's either happened or will happen with at least some if not all of them. I'm also unsure about how Chrome is handling it.
 
It's called a CRL, or Certificate Revocation List.

Your browser checks SSL certs against it too see if they have been revoked by the issuer.
 
I'd like to see that asshole try. Microsoft has their Update service locked up tighter than Fort Knox.

That. And the fact that Windows Update relies on more factors of authentication than just a cert. This guy is a goofball. Moxie Marlinspike debunked all of his claims - and his l33t hax0r skillz in his most recent Blackhat session:

http://tech.slashdot.org/story/11/09/08/1454221/Moxie-Marlinspikes-Solution-To-the-SSL-CA-Problem

"In his Blackhat talk on the past and future of SSL (YouTube video) Moxie Marlinspike explains the problems of SSL today, and the history of how it came to be so. He then goes on to not only propose a solution, but he's implemented it as well: Convergence.

Skip to 5:20 and start hearing about how amazing this script kiddie isn't.
 
WRONG.. if you mean the hacker didn't get away with it for very long as, unfortunately, he did. The following is quoting Steve Gibson on his "Security Now" podcast (episode 317) from Sept 8 reading a statement from Mozilla..



Can find the podcast audio and/or transcript at http://www.grc.com/securitynow.htm

128970342624121974.jpg

Quoting Steve Gibson is not compelling evidence he has been a "sky is falling" type for a long time. He went all "OMG the world is fucked!" when MS introduced raw sockets in XP and of course it was no big deal.
 
Quoting Steve Gibson is not compelling evidence he has been a "sky is falling" type for a long time. He went all "OMG the world is fucked!" when MS introduced raw sockets in XP and of course it was no big deal.

This.
 
We got one person online, and the workload is enough for like ten users. I think we got a hacker.
 
All if his certificates have been invalidated. No browser, excecpt safari will accept them.
Microsoft also pulled any accpetance of the certs from windows itself, which if I read correctly from another site, is the same place IE gets its info from.

Safari get's its certificate from Internet Explorer on windows. OSX received an update on the 9th to block it too.
 
Back
Top