Attacks/Breaches
1/3/2013
05:40 PM
50%
50%

Phony Google Digital Certificate Blocked By Browser Vendors

Google, Microsoft, and Mozilla are each addressing the problem with security updates to protect users

Google, Microsoft, and Mozilla have decided to revoke trust in two digital certificates improperly issued by a Turkish certificate authority (CA).

The situation came to light Christmas Eve when Google Chrome detected and blocked an unauthorized digital certificate for the "*.google.com" domain.

"We investigated immediately and found the certificate was issued by an intermediate certificate authority (CA) linking back to TURKTRUST, a Turkish certificate authority," blogged Adam Langley, Google Software Engineer. "Intermediate CA certificates carry the full authority of the CA, so anyone who has one can use it to create a certificate for any website they wish to impersonate."

As a result of the detection of the rogue certificate, Google updated Chrome's certificate revocation metadata on Dec. 25 to block the intermediate CA, and then alerted TURKTRUST and other browser vendors.

"TURKTRUST told us that based on our information, they discovered that in August 2011 they had mistakenly issued two intermediate CA certificates to organizations that should have instead received regular SSL certificates," Langley continued. "On December 26, we pushed another Chrome metadata update to block the second mistaken CA certificate and informed the other browser vendors."

According to Microsoft, the intermediate certificate authorities TURKTRUST created were (*.EGO.GOV.TR and e-islam.kktcmerkezbankasi.org). It was the *.EGO.GOV.TR subsidiary CA then used to issue a fraudulent digital certificate to *.google.com, Microsoft notes in a customer advisory.

To address the issue, the company updated the Certificate Trust List (CTL) to remove the trust of the certificates causing the issue.

Mozilla, meanwhile, is "actively revoking trust" for the certificates in an update, blogged Michael Coates, Mozilla's director of security assurance, adding that users can expect a Firefox update Jan. 8.

"This is not a Firefox-specific issue," he explained. "Nevertheless, we are concerned that at least one of the mis-issued intermediate certificates was used for man-in-the-middle (MITM) traffic management of domain names that the customer did not legitimately own or control. We are also concerned that the private keys for these certificates were not kept as secure as would be expected for intermediate certificates."

"We have also suspended inclusion of the “TÜRKTRUST Bilgi İletişim ve Bilişim Güvenliği Hizmetleri A.Ş. (c) Aralık 2007” root certificate, pending further review," he added.

In 2011, CA security received increased attention due to a number of security incidents, including an attack on DigiNotar that led to browser vendors revoking hundreds of fraudulent SSL certificates and ultimately forced the company into bankruptcy.

In light of the most recent situation, Google announced plans to update Chrome again later this month to no longer indicate Extended Validation status for certificates issued by TURKTRUST, though connections to TURKTRUST-validated HTTPS servers may continue to be allowed, Langley blogged.

"Since our priority is the security and privacy of our users, we may also decide to take additional action after further discussion and careful consideration," he added.

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Comment  | 
Print  | 
More Insights
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-2014-6090
Published: 2015-04-27
Multiple cross-site request forgery (CSRF) vulnerabilities in the (1) DataMappingEditorCommands, (2) DatastoreEditorCommands, and (3) IEGEditorCommands servlets in IBM Curam Social Program Management (SPM) 5.2 SP6 before EP6, 6.0 SP2 before EP26, 6.0.3 before 6.0.3.0 iFix8, 6.0.4 before 6.0.4.5 iFix...

CVE-2014-6092
Published: 2015-04-27
IBM Curam Social Program Management (SPM) 5.2 before SP6 EP6, 6.0 SP2 before EP26, 6.0.4 before 6.0.4.6, and 6.0.5 before 6.0.5.6 requires failed-login handling for web-service accounts to have the same lockout policy as for standard user accounts, which makes it easier for remote attackers to cause...

CVE-2015-0113
Published: 2015-04-27
The Jazz help system in IBM Rational Collaborative Lifecycle Management 4.0 through 5.0.2, Rational Quality Manager 4.0 through 4.0.7 and 5.0 through 5.0.2, Rational Team Concert 4.0 through 4.0.7 and 5.0 through 5.0.2, Rational Requirements Composer 4.0 through 4.0.7, Rational DOORS Next Generation...

CVE-2015-0174
Published: 2015-04-27
The SNMP implementation in IBM WebSphere Application Server (WAS) 8.5 before 8.5.5.5 does not properly handle configuration data, which allows remote authenticated users to obtain sensitive information via unspecified vectors.

CVE-2015-0175
Published: 2015-04-27
IBM WebSphere Application Server (WAS) 8.5 Liberty Profile before 8.5.5.5 does not properly implement authData elements, which allows remote authenticated users to gain privileges via unspecified vectors.

Dark Reading Radio
Archived Dark Reading Radio
Join security and risk expert John Pironti and Dark Reading Editor-in-Chief Tim Wilson for a live online discussion of the sea-changing shift in security strategy and the many ways it is affecting IT and business.