Hackers gang up on Kaminsky over DNS flaw

But it's humble pie all round for vocal critics.

Computer security professionals have ganged up on Dan Kaminsky for violating a cardinal rule of hackerdom: publicising a flaw without providing the technical details to verify the finding.

Kaminsky made headlines earlier this week by talking about a major flaw in the DNS software used to connect computers to each other on the Internet. In late March he grouped together 16 companies that make DNS software - companies like Microsoft, Cisco and Sun Microsystems - and talked them into fixing the problem and jointly releasing patches for it.

On Wednesday this week, he took things a step further on his blog, asking hackers to avoid researching the problem until next month, when he plans to release more information about it at the Black Hat security conference.

He said he wanted to go public with the issue to put pressure on corporate IT staff and Internet service providers to update their DNS software, while at the same time keeping the bad guys in the dark about the precise nature of the problem. A full public disclosure of the technical details would make the Internet unsafe, he said. "Right now, none of this stuff needs to go public."

He quickly received a sceptical reaction from Matasano Security researcher Thomas Ptacek, who blogged that Kaminsky's cache poisoning attack is merely one of many disclosures underlining the same well-known problem with DNS -- that it does not do a good enough job in creating random numbers to create unique "session ID" strings when communicating with other computers on the Internet.

"The bug in DNS is that it has a 16-bit session ID," he said via an e-mail Wednesday. "You can't deploy a new Web app with less than 128-bit session IDs. We've known about that fundamental problem since the '90s."

"Here comes the onslaught of interviews and media explosion for another overhyped bug by Dan Kaminsky," wrote a jaded (and anonymous) poster to the Matasano blog.

Over at the SANS Internet Storm Center, one blogger speculated that Kaminsky's bug had actually been disclosed three years earlier.

The flaw appears to be a serious one that could be exploited in what's called a "cache poisoning attack". These attacks hack the DNS system, using it to redirect victims to malicious websites without their knowledge. They have been known about for years but can be hard to pull off.

But Kaminsky claims to have found a very effective way of launching such an attack, thanks to a vulnerability in the design of the DNS surprised" by some of the negative reaction, but that this kind of scepticism was vital to the hacker community. "I'm breaking the rules," he admitted. "There's not enough information in the advisory to figure out the attack and I'm bragging about it."

According to DNS expert Paul Vixie, one of the few people who has been given a detailed briefing on Kaminsky's finding, it is different from the issue reported three years ago by SANS. While Kaminsky's flaw is in the same area, "it's a different problem", said Vixie, who is president of the Internet Systems Consortium, the maker of the most widely used DNS server software on the Internet.

The issue is urgent and should be patched immediately, said David Dagon, a DNS researcher at Georgia Tech who was also briefed on the bug. "With sparse details, a few have questioned whether Dan Kaminsky had repackaged older work in DNS attacks," he said. "It is not feasible to think that the world's DNS vendors would have patched and announced in unison for no reason."

By day's end, Kaminsky had even turned his most vocal critic, Matasano's Ptacek, who issued a retraction on this blog after Kaminsky explained the details of his research over the telephone. "He has the goods," Ptacek said afterward. While the attack builds on previous DNS research, it makes cache poisoning attacks extremely easy to pull off. "He's pretty much taken it to point and click to an extent that we didn't see coming."

Kaminsky's remaining critics will have to wait until his 7 August Black Hat presentation to know for sure, however.

The security researcher said he hopes that they show up for his talk. "If I do not have the exploit," he said. "I deserve every single piece of anger and distrust."


What are your views on this subject? Use the form below to post a comment on this article up to 500 characters.


Characters remaining: 500

Add your commentComments

What is all the fuss about | Published: 19:58 GMT, 10 July 2008

If the major DNS suppliers did release patches, then one of them is ISC, that patched bind8 and bind9. These are open source. should not be too difficult to see what they changed and see to what kind of vulnerability it points. At least one can narrow the search.

Related Security news

Microsoft denies building security 'backdoor' in Windows 7

Privacy organisations shouldn't read too much into NSA involvement it says

Pentagon expands exclusive deal with McAfee

Department of Defense uses McAfee products

Police arrest pair over global banking web scam

Man and woman arrested in Manchester for using notorious Zeus Trojan

Security star Fortinet sets price for IPO

Investors still have taste for tech.



Email this article to a friend or colleague:


PLEASE NOTE: Your name is used only to let the recipient know who sent the story, and in case of transmission error. Both your name and the recipient's name and address will not be used for any other purpose.

Techworld White Papers

Database security: Preventing enterprise data leaks at the source

IDC discusses the growing internal threats to business information, the impact of government regulations on the protection of data, and how enterprises must adopt database security best practices...

Download Whitepaper

Service-oriented security

SOA has become an integral part of enterprise software by providing a framework to efficiently develop software as services that is easily sharable, reusable, and integrated. No where is the need more apparent than in the Identity Management space. Welcome to the age of Service-Oriented Security (SOS).

Download Whitepaper

Data protection prospective vendor checklist

Organisations need a way to map business needs against all these challenges in procuring a technical solution. To help, SANS has developed the following Prospective Vendor Checklist.

Download Whitepaper

Unlock the power of the mainframe

This whitepaper presents the notion of CICS as an integration hub based on a component-based, service-oriented architecture supporting Web services. Highlights will review the challenges and contrasted support for Web services natively in CICS.

Download Whitepaper

Techworld UK - Technology - Business

COLT White Paper

Are all VoIP services the same?

Questions to ask your service provider to ensure you get the VoIP service you need
With careful choice of partner, your business can have all the advantages of VoIP access - reduced costs, flexibility and simplicity - without the drawbacks.
This white paper is your guide to ensure you get right the VoIP service and details the pitfalls which businesses would do well to avoid.

Download white paper
BMC

Ride the express lane in the journey to speed ITIL adoption

Explore the challenges in making the journey to ITIL and the criteria for selecting consulting services
By following ITIL practices, your IT organisation will become more closely integrated with the business. We recommend making the journey to ITIL in a sequence of six incremental steps, the phases of which are driven through execution of a strategic transformational roadmap.

Download white paper

Webcast: IT Financial Management: Cost Optimisation for Efficiency and Agility.
On Demand Webcast
Join this webcast to learn about the techniques and technologies that can help you prove the value of IT to the business by understanding the true cost of today's IT services and those that will be necessary to deliver future success.

Register Today

Site Map

IDG Network

* *