Closed Bug 1988663 Opened 1 year ago Closed 1 year ago

Revoked TLS Certificate for https://revoked-isrgrootx1.letsencrypt.org shows as valid and safe

Categories

(Core :: Security: PSM, defect, P3)

Firefox 142
defect

Tracking

()

RESOLVED FIXED

People

(Reporter: dundir, Unassigned)

References

()

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:142.0) Gecko/20100101 Firefox/142.0

Steps to reproduce:

I visited https://revoked-isrgrootx1.letsencrypt.org/

Actual results:

The page loads silently without error or notification that the certificate has been revoked.

Expected results:

The page should have shown a security warning that the TLS Certificate was expired or revoked.

The Bugbug bot thinks this bug should belong to the 'Core::Security: PSM' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Security: PSM
Product: Firefox → Core

Thanks for this report. I've written up my analysis in https://github.com/mozilla/crlite/issues/367.

Severity: -- → S3
Priority: -- → P3

updating summary -- it's a specific problem and not generically multiple certs, though it could be more than just this one. I believe LetsEncrypt has dropped their OCSP server so in practice this certificate is unlikely to be revoked in any other browser, either, or in firefox if you disable CRLite and fall back to requiring OCSP.

To maybe save someone a trip, the summary of the github issue is

Certificates revoked within one CT log MMD of issuance can fail to appear as revoked in delta updates

Summary: Revoked TLS Certificates show as valid and safe → Revoked TLS Certificate for https://revoked-isrgrootx1.letsencrypt.org shows as valid and safe

Thank you all for looking into this. It appears that as of early this morning, or potentially sometime yesterday the revocation for the certificate hosted at the site in question is now properly showing that the certificate has been revoked.

In terms of properly setting expectations surrounding certificate revocation, I'm wondering if possibly LetsEncrypt changed something (to correct the false negative), or if this is just as expected and the 45 day bound (mentioned wrt current configuration) just happened to be much sooner in practice (cert was issued Sep 10th for reference).

As the specific steps to replicate are now no longer valid for this issue, and the issue is now fixed (?), should this bug be closed?

We'll leave this open until https://github.com/mozilla/crlite/issues/367 is resolved. The https://revoked-isrgrootx1.letsencrypt.org certificate is showing as blocked now because we entered a new 45 day window this morning. In case it's useful, you can tell how far into the 45 day window we are by looking at the timestamp in the oldest entry in https://firefox.settings.services.mozilla.com/v1/buckets/security-state/collections/cert-revocations/records.

The fix in https://github.com/mozilla/crlite/pull/369 has been deployed to our production CRLite instance. The current CRLite filters are missing revocation statuses for certificates that were (1) first logged in CT between 2025-09-23 and 2025-09-29, and (2) revoked within 24 hours of being logged in CT. We do not plan to rotate the CRLite filters off-schedule to pick up these revocations. The next scheduled rotation is 2025-11-07.

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.