Vulnerabilities / Threats // Vulnerability Management
7/29/2014
05:07 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Scan Shows Possible Heartbleed Fix Failures

Study indicates many Global 2000 firms patched, but failed to replace digital certificates.

Of more than 1,600 Global 2000 firms, only 3% of their public-facing servers have been fully and properly locked down from the Heartbleed vulnerability that was first revealed nearly three months ago, new data shows.

While fewer than 1% of the external-facing servers at these enterprises remain fully vulnerable to Heartbleed, some 97% are only partially remediated from the threat, mostly because they failed to replace the private key, or revoke the old digital certificate. By not replacing the private key, an attacker could decrypt SSL traffic from the host, and by failing to revoke the old cert, an attacker could use it in phishing attacks, according to the July 2014 status report by Venafi.

"Heartbleed has been known to the world for 11 weeks now. Yet we still see evidence of thousands of systems susceptible to Heartbleed that have not even been patched yet," says Kevin Bocek, vice president of security strategy and threat intelligence at Venafi, in an email interview. "We believe this is partly due to a 'patch-and-move-on' mentality amongst IT professionals, meaning that once the patch is addressed, they believe the security hole is plugged. This approach is something that must be changed because as attacks continue to evolve and become more sophisticated, remediation becomes more extensive requiring multiple steps aside from just patching the vulnerable system."

But Robert Graham, CEO of Errata Security, says he's skeptical of the data in the report, and that it distorts the issue. He says his own scans show that 90% of externally facing sites don't use OpenSSL in the first place, so they had no reason to revoke and reissue keys.

He says the big issue is about organizations not revoking the at-risk digital certificates. "The paper doesn't mention the exact breakdown, but it's likely that the primary issue is lack of revocation of existing certificates. That is indeed something that many affected organizations haven't done, but should do," he says.

Dan Kaminsky, chief scientist at WhiteOps, says corporations have better processes in place for patching their internal servers than for working with third parties such as certificate authorities. "With an absence of evidence that keys were actually compromised, it wouldn't be surprising that the internal code was updated while the external dependency -- the new certs -- was left unaddressed," Kaminsky says.

He says it's unclear in the report whether the certificates are CA-originated ones or not. "Self-signed certs don't really offer much security at all, Heartbleed or not," he notes.

[Heartbleed wasn't the first security hole discovered in SSL deployments, and it won't be the last. Read SSL After The Heartbleed.]

Meanwhile, the risk of bad guys pilfering private keys was fairly low, says Ivan Ristic, director of Qualys's SSL Labs. That may also explain why organizations appear not to be taking the certificate issue as seriously, he notes.

The full report is available here (PDF) for download.

Kelly Jackson Higgins is Executive Editor at DarkReading.com. 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
securityaffairs
50%
50%
securityaffairs,
User Rank: Ninja
7/31/2014 | 5:21:20 PM
Re: patch only?
I have a few doubts related to the absolute data proposed. As said by Robert Grahamprobably the number of organizations that doesn't use OpenSSL in very high. 

This statement puzzles me about the quality of the "population" analyzed.
"only 3% of Their public-facing servers not have been fully and properly locked down from the Heartbleed vulnerability"
Whoopty
50%
50%
Whoopty,
User Rank: Ninja
7/30/2014 | 10:59:45 AM
Project Zero
I wonder if major bugs like this that affect thousands of sites will become rarer in the future, thanks to efforts like Google's Project Zero security team. They've hired on the likes of Geohotz and several other amazing hackers, so it seems like they'll be able to really shore up the digital defenses of a lot of web properties. 
Kelly Jackson Higgins
50%
50%
Kelly Jackson Higgins,
User Rank: Strategist
7/30/2014 | 9:59:51 AM
Re: patch only?
Thank you for sharing that, Ryan. I'm also curious if any org has a good reason not to patch and reissue the cert.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
7/30/2014 | 9:54:57 AM
Re: patch only?
My institution patched for Heartbleed and cycled the certs. Otherwise you won't be able to confidently say that your systems aren't exploited. The vulnerability may have allowed for forged certs to be applied and if you only patched you would not be able to detect the further exploits of the system. I would be interested to hear the validation for institutions that only patched as well. Might provide some perspective we couldn't think of.
Kelly Jackson Higgins
50%
50%
Kelly Jackson Higgins,
User Rank: Strategist
7/29/2014 | 5:19:16 PM
patch only?
Any of our readers willing to share whether they've only patched for Heartbleed, but not revoked their digital certs? We'd love to hear your perspective on this. 
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-5084
Published: 2015-08-02
The Siemens SIMATIC WinCC Sm@rtClient and Sm@rtClient Lite applications before 01.00.01.00 for Android do not properly store passwords, which allows physically approximate attackers to obtain sensitive information via unspecified vectors.

CVE-2015-5352
Published: 2015-08-02
The x11_open_helper function in channels.c in ssh in OpenSSH before 6.9, when ForwardX11Trusted mode is not used, lacks a check of the refusal deadline for X connections, which makes it easier for remote attackers to bypass intended access restrictions via a connection outside of the permitted time ...

CVE-2015-5537
Published: 2015-08-02
The SSL layer of the HTTPS service in Siemens RuggedCom ROS before 4.2.0 and ROX II does not properly implement CBC padding, which makes it easier for man-in-the-middle attackers to obtain cleartext data via a padding-oracle attack, a different vulnerability than CVE-2014-3566.

CVE-2015-5600
Published: 2015-08-02
The kbdint_next_device function in auth2-chall.c in sshd in OpenSSH through 6.9 does not properly restrict the processing of keyboard-interactive devices within a single connection, which makes it easier for remote attackers to conduct brute-force attacks or cause a denial of service (CPU consumptio...

CVE-2015-1009
Published: 2015-07-31
Schneider Electric InduSoft Web Studio before 7.1.3.5 Patch 5 and Wonderware InTouch Machine Edition through 7.1 SP3 Patch 4 use cleartext for project-window password storage, which allows local users to obtain sensitive information by reading a file.

Dark Reading Radio
Archived Dark Reading Radio
What’s the future of the venerable firewall? We’ve invited two security industry leaders to make their case: Join us and bring your questions and opinions!