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.


Comodo Warns Of VeriSign SSL Vulnerability

VeriSign said the supposed certificate request flaw is actually a feature and accused Comodo of not following standard vulnerability disclosure guidelines.

Internet security and digital certificate provider Comodo on Wednesday warned of a "major security vulnerability" for any VeriSign customer relying on SSL digital certificates. In particular, Comodo said in a statement that it had accessed a major financial institution's VeriSign customer account without having to first authenticate.

"When we uncovered this serious security vulnerability, we knew we had to do the right thing to notify VeriSign immediately to correct the design problem," said Melih Abdulhayoglu, Comodo CEO, in the statement. "With millions of [customers'] financial transactions at stake, we wasted no time to help correct the problem even though it wasn't ours to begin with."

Comodo said it followed vulnerability disclosure guidelines per the Common Computing Security Standards (CCSS), using an independent go-between to alert VeriSign to the problem.

VeriSign, which is a competitor of Comodo's, handles more than 175 million SSL, identity, authentication, and domain name services queries every day, across more than 90,000 websites in 160 countries. But VeriSign denies that any such vulnerability exists, saying that the alleged flaw is actually a feature.

"Many large enterprises use a workflow whereby individuals within the organization can request SSL certificates for the projects they're working on. Requests from these pages go to administrators, who then evaluate whether or not to issue the certificates," said Tim Callan, product marketing executive for VeriSign's SSL business unit, in a blog post.

Being able to access these certificate-request pages, in other words, is not the same as being able to obtain one, he said. "By their nature these pages are publicly accessible, and access to these pages does not constitute a security flaw. There is no private information available from these pages, and certificate requests go through evaluation by the enterprise's designated certificate administration body before any certificate is issued."

Beyond dismissing the vulnerability, Callan also criticized Comodo for not following CCSS vulnerability-disclosure guidelines. "These guidelines clearly state that the discloser and the security vendor will mutually negotiate the strategy and timeline for both disclosure and mitigation of the vulnerability." But Comodo failed to make clear either the timing or content of its disclosure, he said, or to collaborate on "a safe disclosure schedule" that would have helped protect customers from zero-day attacks, if it had been an actual vulnerability.

One commenter to Callan's blog, however, questioned the threat that these publicly available request pages posed in the hands of a disgruntled insider at VeriSign or one of its customers. "Currently we are customers of yours, and a piece of fax paper on 'company letterhead' is all that seems to stand in our way of domain ownership and/or SSL certificate enrollment," the respondent wrote. "What are the real secondary or tertiary measures a company can take to ensure important certificates cannot be accessed so trivially?"

Perhaps to underscore the delicate nature of authenticating identities online, the commenter signed himself as well-known security researcher "Marcus Ranum." The only problem? When reached for comment, Ranum said it wasn't him.

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
SOC 2s & Third-Party Assessments: How to Prevent Them from Being Used in a Data Breach Lawsuit
Beth Burgin Waller, Chair, Cybersecurity & Data Privacy Practice , Woods Rogers PLC,  12/5/2019
Navigating Security in the Cloud
Diya Jolly, Chief Product Officer, Okta,  12/4/2019
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2019-12-06
domain/section/markdown/markdown.go in Documize before 3.5.1 mishandles untrusted Markdown content. This was addressed by adding the bluemonday HTML sanitizer to defend against XSS.
PUBLISHED: 2019-12-06
An Insecure Direct Object Reference (IDOR) vulnerability in the Xtivia Web Time and Expense (WebTE) interface used for Microsoft Dynamics NAV before 2017 allows an attacker to download arbitrary files by specifying arbitrary values for the recId and filename parameters of the /Home/GetAttachment fun...
PUBLISHED: 2019-12-06
phpMyAdmin before 4.9.2 does not escape certain Git information, related to libraries/classes/Display/GitRevision.php and libraries/classes/Footer.php.
PUBLISHED: 2019-12-05
A Cross-Site Scripting (XSS) vulnerability exists in LDAP Account Manager (LAM) Pro 3.6 in the filter parameter to cmd.php in an export and exporter_id action. and the filteruid parameter to list.php.
PUBLISHED: 2019-12-05
A Cross-Site Scripting (XSS) vulnerability exists in LDAP Account Manager (LAM) Pro 3.6 in the export, add_value_form, and dn parameters to cmd.php.