Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

2/19/2009
01:44 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Kaminsky Calls For DNSSEC Adoption

Researcher who discovered big DNS vulnerability gets behind DNSSEC, points out steps needed to implement it

WASHINGTON -- BLACK HAT DC -- The much-debated protocol to help secure the Domain Name System received a big boost today when DNS security guru Dan Kaminsky said the industry must adopt the DNSSEC protocol.

Kaminsky, who discovered the now-infamous big DNS flaw last year and got the vendor community to patch it, had for some time mostly dismissed DNSSEC as a DNS security solution. But after studying the specification more closely, Kaminsky -- who discussed his newfound support for DNSSEC here during his Black Hat DC presentation -- said DNSSEC could remedy some of DNS' security weaknesses.

"I was never anti-DNSSEC -- I was just never for it. It just didn't look like it was going to work," Kaminsky said in an interview today. "This is my first time publicly saying we need to do it. No one is more surprised than I."

The federal government is already on its way to widespread DNSSEC adoption after initially only recommending it for some systems. A new federal policy (PDF) issued in the wake of the DNS flaw scare last summer mandates that all federal agencies adopt DNSSEC by December 2009 for their DNS servers.

DNSSEC has been criticized for its complexity, as well as the DNS infrastructure overhaul its adoption typically entails. For DNSSEC's validation model to work for DNS servers, it has to be adopted from end to end, for instance, an issue that is rife with both technical and political challenges.

And DNSSEC requires significant manual configuration, including the signing of encryption keys and updating records, Kaminsky noted.

"The protocol isn't bad. It just has too many [manual] knobs," Kaminsky said. "We have to figure out how to shrink the number of knobs and to automate this. And this is not an impossible task."

DNS servers should be able to generate encryption keys and automatically sign records themselves, for example, he said. And DNSSEC also must be made more scalable than it is today.

"The implementations out there today are not fun to deploy," he said during his presentation. "We need to start migrating new apps to DNSSEC, so end to end you are able to use federated trust."

Why the change of heart for Kaminsky on DNSSEC? "These [DNS] attacks are no longer theoretical," he said. Somewhere between 1 and 3 percent of unpatched servers have already been hit by cache-poisoning attacks, according to data gathered recently by Georgia Tech data, and those are only the ones the researchers are monitoring. Meanwhile, one-third of all servers remain unpatched for the big DNS bug, he said.

It's time to get DNSSEC rolled out -- but with some key improvements, he said. "My argument is that we need to make DNSSEC deployable today," Kaminsky said.

Among those improvements, according to Kaminsky: The most popular type of DNS server, BIND, must be retrofitted to better support DNSSEC, and root servers need to digitally sign or authenticate DNS traffic. "We also need to work with the interaction among registrars," he said. "DNSSEC solves the problem of getting secure data back out, but how do you get data into .com and .org? Authoritative [DNS] servers today don't interact with their parents...Name servers need a way to automatically inform their parents [.com, .org] that they have the keying material."

Even with these issues, DNSSEC is still the best solution for cross-organizational authentication. "DNSSEC is the key to fixing the persistent authentication problems plaguing real-world, cross-organizational business for years," Kaminsky said.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 10/23/2020
7 Tips for Choosing Security Metrics That Matter
Ericka Chickowski, Contributing Writer,  10/19/2020
Russian Military Officers Unmasked, Indicted for High-Profile Cyberattack Campaigns
Kelly Jackson Higgins, Executive Editor at Dark Reading,  10/19/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-24847
PUBLISHED: 2020-10-23
A Cross-Site Request Forgery (CSRF) vulnerability is identified in FruityWifi through 2.4. Due to a lack of CSRF protection in page_config_adv.php, an unauthenticated attacker can lure the victim to visit his website by social engineering or another attack vector. Due to this issue, an unauthenticat...
CVE-2020-24848
PUBLISHED: 2020-10-23
FruityWifi through 2.4 has an unsafe Sudo configuration [(ALL : ALL) NOPASSWD: ALL]. This allows an attacker to perform a system-level (root) local privilege escalation, allowing an attacker to gain complete persistent access to the local system.
CVE-2020-5990
PUBLISHED: 2020-10-23
NVIDIA GeForce Experience, all versions prior to 3.20.5.70, contains a vulnerability in the ShadowPlay component which may lead to local privilege escalation, code execution, denial of service or information disclosure.
CVE-2020-25483
PUBLISHED: 2020-10-23
An arbitrary command execution vulnerability exists in the fopen() function of file writes of UCMS v1.4.8, where an attacker can gain access to the server.
CVE-2020-5977
PUBLISHED: 2020-10-23
NVIDIA GeForce Experience, all versions prior to 3.20.5.70, contains a vulnerability in NVIDIA Web Helper NodeJS Web Server in which an uncontrolled search path is used to load a node module, which may lead to code execution, denial of service, escalation of privileges, and information disclosure.