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

7/30/2009
01:17 AM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Black Hat: PKI Hack Demonstrates Flaws in Digital Certificate Technology

Researcher Dan Kaminsky illuminates flaws in X.509 authentication

BLACK HAT USA -- LAS VEGAS -- The spotlight here this week was on another potentially broken piece of the Internet infrastructure as renowned white-hat hacker Dan Kaminsky today revealed critical bugs in the X.509 authentication scheme.

Kaminsky, who rocked the security community last year with his major DNS flaw find, said the potential for an X.509 meltdown and major hack is high, but not likely possible for at least another six months. "You can wait for it to blow up, or do something about it," says Kaminsky, director of penetration testing for IOActive. "This time, I don't want to see anything get 'owned.'"

Ironically, Kaminsky himself today was recovering from a targeted attack on his Website, email and Twitter accounts by a group of black hat hackers who stole passwords, emails, instant message chats from Kaminsky and former hacker Kevin Mitnick, and posted the information online. Kaminsky dismissed the attack "as nothing technically interesting" and likely began with a Web-borne exploit, he says.

Around 60 percent of attacks are due to weak or default passwords. "X.509 was supposed to be the solution" in authentication, Kaminsky says. "Businesses have spent hundreds of millions of dollars of investment in it. But there are things wrong structurally and technically with X.509." X.509 doesn't scale well, he says, and it can't delegate authority to issue certificates, for instance.

He noted that one of VeriSign's core root servers until recently used the older and weaker MD2 hash algorithm to sign certificates. "If a certificate is signed with MD2, it can accept everything," he says.

VeriSign no longer uses MD2 to sign any of its digital certificates, says Tim Callan, vice president of product marketing at VeriSign. "Last year, VeriSign implemented a process for transitioning off MD2 and, as of May 17th, the transition to the SHA-1 algorithm has been completed," he says.

Even so, browsers today still come with legacy [MD2] root certificates, Kaminsky says. "VeriSign's fix is to give new browsers something to ship. Microsoft, et al, are about making the old browsers ignore MD2 even if it is there. Both paths are helpful," he says.

Meanwhile, Kaminsky pointed to the work of another researcher who presented at Black Hat, Moxie Marlinspike, who demonstrated an attack that spoofs SSL certificates by adding a "null" string character to the certificate fields to fake out the browser. Moxie also added this null-termination attack to an existing hacking tool he developed.

"This is a wonderful example of what I'm talking about," Kaminsky says. "Moxie and I have the same core attack here -- he did this year what I did last year. We both went for the null" string attack, he says. Moxie was able to force a Firefox browser to download a code "update" over SSL with his phony digital certificate, Kaminsky says.

VeriSign's Callan says none of VeriSign's certificate brands or sub-bands have a domain containing a null character. "Marlinspike's presentation underscores the importance of such stringent issuance practices by CAs to ensure the integrity of online security," Callan says.

Ultimately, the answer is to move to DNSSEC, Kaminsky says. "We're going to have the DNS root signed [by DNSSEC] by the end of the year, so then we can build a new PKI with exclusion and delegation" capabilities, he says.

"Today, Dan Kaminsky revealed more important research that will surely serve to raise awareness on the need for ongoing enhancements to Internet infrastructure standards," VeriSign's Callan says.

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
Manchester United Suffers Cyberattack
Dark Reading Staff 11/23/2020
As 'Anywhere Work' Evolves, Security Will Be Key Challenge
Robert Lemos, Contributing Writer,  11/23/2020
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-29367
PUBLISHED: 2020-11-27
blosc2.c in Blosc C-Blosc2 through 2.0.0.beta.5 has a heap-based buffer overflow when there is a lack of space to write compressed data.
CVE-2020-26245
PUBLISHED: 2020-11-27
npm package systeminformation before version 4.30.5 is vulnerable to Prototype Pollution leading to Command Injection. The issue was fixed with a rewrite of shell sanitations to avoid prototyper pollution problems. The issue is fixed in version 4.30.5. If you cannot upgrade, be sure to check or sani...
CVE-2017-15682
PUBLISHED: 2020-11-27
In Crafter CMS Crafter Studio 3.0.1 an unauthenticated attacker is able to inject malicious JavaScript code resulting in a stored/blind XSS in the admin panel.
CVE-2017-15683
PUBLISHED: 2020-11-27
In Crafter CMS Crafter Studio 3.0.1 an unauthenticated attacker is able to create a site with specially crafted XML that allows the retrieval of OS files out-of-band.
CVE-2017-15684
PUBLISHED: 2020-11-27
Crafter CMS Crafter Studio 3.0.1 has a directory traversal vulnerability which allows unauthenticated attackers to view files from the operating system.