Revealed: The Internet's Biggest Security Hole

HardOCP News

[H] News
Joined
Dec 31, 1969
Messages
0
Two security researchers have demonstrated an exploit that would allow someone to intercept internet traffic anywhere in the world undetected. Attackers could even modify the intercepted information before it reaches its destination without anyone being the wiser. Thanks to Dave A. for the linkage.

"It's a huge issue. It's at least as big an issue as the DNS issue, if not bigger," said Peiter "Mudge" Zatko, noted computer security expert and former member of the L0pht hacking group, who testified to Congress in 1998 that he could bring down the internet in 30 minutes using a similar BGP attack, and disclosed privately to government agents how BGP could also be exploited to eavesdrop.
 
This is just one of many methods unfortunately. If you know how, you could go onto any college network and do a similar feet.
 
The Internet's biggest security hole: The human beings in front of the computers. True story.
 
Why would any hackers take the time to do this.
If you have no morals there are much easier ways to steal money on the internet*.

*"How to Catch an ID theif"-Dateline NBC
 
There was no mention of Justin in that article......oh "security" hole. Sorry.
 
I think undetected goes a bit far.

It is possible to discover that someone is eavesdropping on you using this method if you pay attention to which routes are being added and removed.

My thoughts on defending against this is to not allow updates from anything other than routers you know are trustworthy, though this would be cumbersome for some situations.

It's also another reason to assume that every box on the internet is owned and always use high strength encryption if you're doing anything confidential.
 
<threadjack>
Did anyone fix that DNS hole? I mean, is it something that everyone that has a PC connected to the net has to fix or what? The details were sketchy...
 
I can definitely agree that this is a problem. I don't tell my passwords to anyone. But some people know where I was born, for instance. And it's not regarded as sensitive information in normal conversation, so they could have told anyone. And there are tons more people who know what my mother's maiden name is.

If these pieces of information could make it possible to obtain or reset my password, my password is therefore only as secure as that weakest link. Kind of scary.

As a side note for riot8ap, the DNS vulnerability is quasi-bandaided at this point. Dan Kaminsky worked with a lot of the core companies to develop and apply a patch that significantly *reduces*--but does not eliminate--the threat. It's meant to buy time while they develop a complete fix. Unfortunately, the current fix hasn't been applied by some organizations (companies, ISPs--the bottom level of the DNS hierarchy, I think), leaving vulnerable networks. End users shouldn't have to do anything, though. You can check if your network is vulnerable at Kaminsky's site (http://www.doxpara.com/) and if so, you can always switch to OpenDNS.
 
Crap, I'm a noob and replied to the wrong thread (hey, there were two security stories right next to each other). The DNS vulnerability info is still relevant, though!

I can definitely agree that this is a problem. I don't tell my passwords to anyone. But some people know where I was born, for instance. And it's not regarded as sensitive information in normal conversation, so they could have told anyone. And there are tons more people who know what my mother's maiden name is.

If these pieces of information could make it possible to obtain or reset my password, my password is therefore only as secure as that weakest link. Kind of scary.

As a side note for riot8ap, the DNS vulnerability is quasi-bandaided at this point. Dan Kaminsky worked with a lot of the core companies to develop and apply a patch that significantly *reduces*--but does not eliminate--the threat. It's meant to buy time while they develop a complete fix. Unfortunately, the current fix hasn't been applied by some organizations (companies, ISPs--the bottom level of the DNS hierarchy, I think), leaving vulnerable networks. End users shouldn't have to do anything, though. You can check if your network is vulnerable at Kaminsky's site (http://www.doxpara.com/) and if so, you can always switch to OpenDNS.
 
Back
Top