2025-04-22
Flawed SSL.com DCV Issues Unvalidated Certificates
Certificate authority SSL.com has revoked 11 certificates after a researcher reported a bug in a domain control validation (DCV) method that would allow a user to erroneously validate their ownership of the domain of their verification email address. SSL.com allows DCV establishment via email challenge response, including validation through a DNS TXT record, but the site's implementation of this method mistakenly adds the domain name of the user's email address to their list of verified domains, allowing a user to then request certificates for that domain. Fraudulently obtained TLS certificates could be abused to create spoofed phishing sites, to decrypt HTTPS traffic and enable man-in-the middle attacks, and more. There is no evidence the now-revoked certificates issued using this bug were obtained maliciously; SSL.com has temporarily disabled this DCV process until the flaw is fixed, and will issue an incident report by May 2, 2025.
Editor's Note
SSL.com revoked the misidentified certificates within 24 hours of discovery. Strong validation of the FQDN/email address is in their certificate practices statement, so these actions are consistent with that and should avoid any motions to make their CA untrusted. With shortened certificate lifecycles, automation is key to survival, which includes automated DCV, which needs to remain both scalable and fraud resistant, which can be opposing forces. Expect providers to be working on these to improve security. Double check your validation mechanism to be sure it's active and consistent with your provider's requirements.

Lee Neely
Issues in implementing the domain ownership verification correctly keep coming up. This should be functionality that is thoroughly tested and reviewed. A lot of effort has been spent in the past to improve the CA ecosystem in recent years, but basic code and implementation quality issues still appear to be a big problem.

Johannes Ullrich
The DCV seems still in flux. I am somewhat surprised, as we do have a working reference protocol for this with ACME, but these things do tend to happen. It's software. Interesting that it's even being looked at and caught. That is the most fascinating part of the story.
