Wired’s Joshua A Davis has a great profile of Dan Kaminsky’s work on discovering and then helping to fix a net-crashing DNS bug earlier this year. Davis really captures the excitement of discovering a major security flaw and the complex web of personal, professional and technical complications that come to bear when you’re trying to disclose the research in a way that minimizes harm to the net.
Dan does a lot of fun security-related stuff that doesn’t get talked about in public. There’s this one thing he does —
But that would be telling…
The next morning, Kaminsky strode to the front of the conference room at Microsoft headquarters before Vixie could introduce him or even welcome the assembled heavy hitters. The 16 people in the room represented Cisco Systems, Microsoft, and the most important designers of modern DNS software.Vixie was prepared to say a few words, but Kaminsky assumed that everyone was there to hear what he had to say. After all, he’d earned the spotlight. He hadn’t sold the discovery to the Russian mob. He hadn’t used it to take over banks. He hadn’t destroyed the Internet. He was actually losing money on the whole thing: As a freelance computer consultant, he had taken time off work to save the world. In return, he deserved to bask in the glory of discovery. Maybe his name would be heralded around the world.
Kaminsky started by laying out the timeline. He had discovered a devastating flaw in DNS and would explain the details in a moment. But first he wanted the group to know that they didn’t have much time. On August 6, he was going to a hacker convention in Las Vegas, where he would stand before the world and unveil his amazing discovery. If there was a solution, they’d better figure it out by then.
But did Kaminsky have the goods? DNS attacks were nothing new and were considered difficult to execute. The most practical attack—widely known as cache poisoning—required a hacker to submit data to a DNS server at the exact moment that it updated its records. If he succeeded, he could change the records. But, like sperm swimming toward an egg, whichever packet got there first—legitimate or malicious—locked everything else out. If the attacker lost the race, he would have to wait until the server updated again, a moment that might not come for days. And even if he timed it just right, the server required a 16-bit ID number. The hacker had a 1-in-65,536 chance of guessing it correctly. It could take years to successfully compromise just one domain.
The experts watched as Kaminsky opened his laptop and connected the overhead projector. He had created a “weaponized” version of his attack on this vulnerability to demonstrate its power. A mass of data flashed onscreen and told the story. In less than 10 seconds, Kaminsky had compromised a server running BIND 9, Vixie’s DNS routing software, which controls 80 percent of Internet traffic. It was undeniable proof that Kaminsky had the power to take down large swaths of the Internet.
Related Posts: On this day...
- This is how multitasking should be handled in iOS - 2011
- Stripper in Oklahoma City Airport Security - 2010
- Amazon Pulls Plug on Wikileaks - 2010
- Paolo Bacigalupi's SHIP BREAKER: An adventure story in a post-peak-oil world - 2010
- Our Meth House - 2010
- Street Fighter 4 for PS3 or Xbox 360 for $25 shipped - 2009
- A Traffic Light Augmented by Progress Bars - 2009
- Florida State Offensive Lineman sits still while play goes on - 2009
- Unlocking the iPhone 3G... the Vietnamese way - 2008
- UK, Australia, Pennsylvania Speed Traps Thwarted - 2008