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.


06:00 PM
Connect Directly

Security Growing Pangs Loom For 100K+ Sites With Newly Untrusted Certificates

Mozilla revokes 1024-bit root certificates in bid to improve Firefox security and similar changes to come for Chrome as Google plans to dump SHA-1 certificates.

As browser developers try to push the industry toward safer certificate standards, it won't come without some pain: Tens of thousands of sites are already experiencing that following a move last week by Mozilla to revoke a number of root certificates using 1024-bit keys. According to security researchers, that's the approximate number of sites left untrusted as a result of Mozilla's not-so-subtle push to get developers to upgrade their SSL protections with certificates utilizing 2048-bit keys.

According to Mozilla, the company is forcing migration away from 1024-bit certificate in phases, so at the moment it has only revoked select certificates from Entrust, SECOM, GoDaddy, EMC/RSA, Symantec/VeriSign, and NetLock. It will wait until early 2015 to revoke similar certificates from Thawte, VeriSign, Equifax, and GTE Cybertrust that are operated by Symantec and Verizon Certificate Services. "We are actively working with CAs to retire SSL and Code Signing certificates that have 1024-bit RSA keys in an effort to make the upgrade as orderly as possible, and to avoid having system administrators find themselves in emergency mode because their SSL keys were compromised," says Kathleen Wilson of Mozilla's security engineering team.

However, according to data gathered from HD Moore's Project Sonar internet scanning data collection at Rapid7, the current revocation leaves approximately 107,535 sites in an untrusted state. That may seem bad at first blush, but many of those certificates were already long expired or recently expired in July or August.

"The repeal of trust for these certificates is a sound decision based upon NIST recommendations, and while it initially appeared that a great many sites would be affected, the majority of these sites either have expired certificates or a certificate that expires within the next year," says Jody Nickel, senior platform engineer at Rapid7. "We hope that Chrome and other browsers will also remove these certificates to remove the potential risk involved with these 1024-bit CA keys."

Google is actually on a similar mission as Mozilla to remove potentially insecure certificates. Last week the firm announced plans for gradually sunsetting certificate chains using the SHA-1 encryption algorithm. It'll start with the next release of Chrome 39 at the end of this month and continue through two more releases until first quarter of 2015. The firm points to guidance from both the CA Browser Forum and NIST in the deprecation of SHA-1 as its reasoning for the shift.

"We have seen this type of weakness turn into a practical attack before, with the MD5 hash algorithm," say Chris Palmer and Ryan Sleevi of Google. "We need to ensure that by the time an attack against SHA-1 is demonstrated publicly, the web has already moved away from it."

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Zero-Factor Authentication: Owning Our Data
Nick Selby, Chief Security Officer at Paxos Trust Company,  2/19/2020
44% of Security Threats Start in the Cloud
Kelly Sheridan, Staff Editor, Dark Reading,  2/19/2020
Firms Improve Threat Detection but Face Increasingly Disruptive Attacks
Robert Lemos, Contributing Writer,  2/20/2020
Register for Dark Reading Newsletters
White Papers
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
How Enterprises Are Developing and Maintaining Secure Applications
How Enterprises Are Developing and Maintaining Secure Applications
The concept of application security is well known, but application security testing and remediation processes remain unbalanced. Most organizations are confident in their approach to AppSec, although others seem to have no approach at all. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-02-23
An issue was discovered in SmartClient 12.0. If an unauthenticated attacker makes a POST request to /tools/developerConsoleOperations.jsp or /isomorphic/IDACall with malformed XML data in the _transaction parameter, the server replies with a verbose error showing where the application resides (the a...
PUBLISHED: 2020-02-23
An issue was discovered in SmartClient 12.0. Unauthenticated exploitation of blind XXE can occur in the downloadWSDL feature by sending a POST request to /tools/developerConsoleOperations.jsp with a valid payload in the _transaction parameter.
PUBLISHED: 2020-02-23
An issue was discovered in SmartClient 12.0. The Remote Procedure Call (RPC) loadFile provided by the console functionality on the /tools/developerConsoleOperations.jsp (or /isomorphic/IDACall) URL is affected by unauthenticated Local File Inclusion via directory-traversal sequences in the elem XML ...
PUBLISHED: 2020-02-23
An issue was discovered in SmartClient 12.0. The Remote Procedure Call (RPC) saveFile provided by the console functionality on the /tools/developerConsoleOperations.jsp (or /isomorphic/IDACall) URL allows an unauthenticated attacker to overwrite files via vectors involving an XML comment and /.. pat...
PUBLISHED: 2020-02-23
danfruehauf NetworkManager-ssh before 1.2.11 allows privilege escalation because extra options are mishandled.