The bug, which Let's Encrypt confirmed on February 29 and was fixed two hours after discovery, impacted the way it checked the domain name ownership before issuing new TLS certificates.
As a result, the bug opened up a scenario where a certificate could be issued even without adequately validating the holder's control of a domain name.
The Certification Authority Authorization (CAA), an internet security policy, allows domain name holders to indicate to certificate authorities (CAs) whether or not they are authorized to issue digital certificates for a specific domain name.
Let's Encrypt considers domain validation results good only for 30 days from the time of validation, after which it rechecks the CAA record authorizing that domain before issuing the certificate. The bug — which was uncovered in the code for Boulder, the certificate signing software used by Let's Encrypt — is as follows:
"When a certificate request contained N domain names that needed CAA rechecking, Boulder would pick one domain name and check it N times." In other words, when Boulder needed to parse, for example, a group of 5 domains names that required CAA rechecking, it would check one domain name 5 times as opposed to checking each of the 5 domains once.
The company said the bug was introduced as part of an update back in July 2019.
This means that Let's Encrypt might have issued certificates that it shouldn't have in the first place, as a result of which it's revoking all the TLS certificates that were affected by the bug.
The development comes as Let's Encrypt project announced last week that it had issued its one-billionth free TLS certificate since its launch in 2015.
Let's Encrypt said 2.6 percent of approximately 116 million active certificates are affected — about 3,048,289 — out of which about one million are duplicates of other affected certificates.
Fight AI with AI — Battling Cyber Threats with Next-Gen AI Tools
Ready to tackle new AI-driven cybersecurity challenges? Join our insightful webinar with Zscaler to address the growing threat of generative AI in cybersecurity.Supercharge Your Skills
Affected website owners have until 8PM UTC (3PM EST) March 4 to manually renew and replace their certificates, failing which visitors to the websites will be greeted with TLS security warnings — as the certificates are revoked — until the renewal process is complete.
It's worth noting that the certificates issued by Let's Encrypt are valid for a period of 90 days, and ACME clients such as Certbot are capable of automatically renewing them.
But with Let's Encrypt revoking all impacted certificates, website admins will have to perform a forced renewal to prevent any interruptions.
Besides using the tool https://checkhost.unboundtest.com/ to check if a certificate needs replacement, Let's Encrypt has put together a downloadable list of affected serial numbers, allowing subscribers to check if their websites rely on an affected certificate.
Update: Let's Encrypt Postpones Certificate Revocation
In the latest post, Let's Encrypt team confirmed that over 1.7 million affected certificates have already been replaced before the initial deadline, and also been revoked by their system.
However, the company has now decided to postpone the certificate revocation process for over 1 million certificates, which it believes more likely will not be replaced before the compliance deadline.
That's because Let's Encrypt is not willing to break so many websites and cause inconvenience for their visitors.
So, "we have determined that it is in the best interest of the health of the Internet for us to not revoke those certificates by the deadline," Let's Encrypt said.
"We plan to revoke more certificates as we become confident that doing so will not be needlessly disruptive to Web users."
It also hinted, though the vast majority of the wrongfully issued certificates do not pose a security risk, they still initially decided to revoke all 3 million certificates to comply with the industry standards.