12:05 PM
Connect Directly

Microsoft Warns Of Looming Digital Certificate Deadline

To improve Windows security, a Microsoft security update soon will block access to RSA digital certificates that have a key length of less than 1,024 bits.

11 Security Sights Seen Only At Black Hat
11 Security Sights Seen Only At Black Hat
(click image for larger view and for slideshow)
Memo from Microsoft to Windows administrators: Make sure all of your digital certificates have at least 1,024 bits.

That warning comes as Microsoft prepares to release an automatic security update for Windows on Oct. 9, 2012, that will make longer key lengths mandatory for all digital certificates that touch Windows systems.

Notably, Internet Explorer won't be able to access any website secured using an RSA digital certificate with a key length of less than 1,024 bits. Likewise, without a strong enough certificate, certificate authority service in Windows won't be able to start, ActiveX controls might be blocked, users might not be able to install applications, and Outlook 2010 won't be able to encrypt or digitally sign emails, or communicate with an Exchange server for SSL/TLS communications. In addition, Microsoft warned that after its security update, Operations Manager will be unable to monitor--or discover new instances of--any HP-UX PA-RISC computers that don't have an RSA digital certificate of least 1,024 bits.

Microsoft's move reflects the relative ease with which digital certificates of less than 1,024 bits can now be cracked--or derived--via brute-force attacks. "The private keys used in these certificates can be derived and could allow an attacker to duplicate the certificates and use them fraudulently to spoof content, perform phishing attacks, or perform man-in-the-middle attacks," according to Microsoft.

[ Read Cryptographers Discover Public Key Infrastructure Flaw. ]

The "fix" for keeping up with Microsoft's mandatory security improvement is simple. "For those who find they are using certificates with RSA key lengths of less than 1,024 bits, those certificates will be required to be reissued with at least a 1,024-bit key length," according to a Microsoft Security Resource Center blog post. It also noted that "1,024 should, by the way, be considered a minimum length; the most up-to-date security practices recommend 2048 bits or even better."

Microsoft's security update is available now for download. The company recommends that IT administrators gain familiarity with it, and test any existing processes that might break, before it releases the update via Microsoft Update in October. To help, a Microsoft knowledgebase article, Microsoft Security Advisory: Update for minimum certificate key length details tips and techniques for discovering any digital certificates in use that have a key length of less than 1,024, as well as recommendations for updating them.

The timing of Microsoft's digital certificate spring cleaning has no doubt been driven by the Flame malware, discovered in May, and inside which security experts found built a "collision attack" against the Microsoft Terminal Services encryption algorithm, which allowed the malware to successfully spoof that Windows service and automatically install itself on targeted PCs.

In the eyes of Marc Stevens, a crypto-analyst at the Centrum Wiskunde and Informatica (CWI) in Amsterdam who studied Flame, whoever created that collision attack was practicing "world-class cryptanalysis." But when it comes to malware attacks, what's leading edge quickly becomes commonplace, as known attack techniques get emulated by other attackers, and included as automated options in crimeware toolkits and the open source Metasploit penetration testing toolkit.

Mobile employees' data and apps need protecting. Here are 10 ways to get the job done. Also in the new, all-digital 10 Steps To E-Commerce Security special issue of Dark Reading: Mobile technology is forcing businesses to rethink the fundamentals of how their networks work. (Free registration required.)

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Andrew Hornback
Andrew Hornback,
User Rank: Apprentice
9/8/2012 | 9:00:13 PM
re: Microsoft Warns Of Looming Digital Certificate Deadline
This isn't being accelerated due to Flame.

Sure, it makes the situation sound more dire because there's a (relatively) new threat out there that could take advantage of the inherent vulnerability involved in using shorter keys, but this has been around for a while.

Microsoft has been writing about this on TechNet for a while (see: A Note on Implementation of the Requirement to Issue Longer Key Length Certificates (December 7, 2010)). This revocation of 1024-bit keys has to do with NIST Special Publication 800-131A.

So, no, Microsoft isn't screaming about the sky falling because of Flame or the Terminal Services problem that was known about a while ago... it has to do with Federal cryptographic regulations. And this is something that any Windows Administrator worth their weight in salt has already implemented a remediation plan for.

Andrew Hornback
InformationWeek Contributor
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
Published: 2014-08-22
Unspecified vulnerability on IBM Power 7 Systems 740 before 740.70 01Ax740_121, 760 before 760.40 Ax760_078, and 770 before 770.30 01Ax770_062 allows local users to gain Service Processor privileges via unknown vectors.

Published: 2014-08-22
Multiple cross-site scripting (XSS) vulnerabilities in framework/common/webcommon/includes/messages.ftl in Apache OFBiz 11.04.01 before 11.04.05 and 12.04.01 before 12.04.04 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors, which are not properly handled in a (1)...

Published: 2014-08-22
Unspecified vulnerability in Apache Traffic Server and 5.x before 5.0.1 has unknown impact and attack vectors, possibly related to health checks.

Published: 2014-08-22
Multiple unspecified vulnerabilities in Salt (aka SaltStack) before 2014.1.10 allow local users to have an unspecified impact via vectors related to temporary file creation in (1), (2) salt-ssh, or (3) salt-cloud.

Published: 2014-08-22
Cross-site scripting (XSS) vulnerability in the Host Aggregates interface in OpenStack Dashboard (Horizon) before 2013.2.4, 2014.1 before 2014.1.2, and Juno before Juno-3 allows remote administrators to inject arbitrary web script or HTML via a new host aggregate name.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Three interviews on critical embedded systems and security, recorded at Black Hat 2014 in Las Vegas.