← DigiCert cases
Bugzilla #1646866 Delayed Revocation

DigiCert: Failure to revoke invalid serialNumber EV certificates within 5 days

RESOLVED INVALID DigiCert
This summary was auto-generated by AI and revised by me when needed — accuracy improves with each update. Always refer to the official Bugzilla thread as the authoritative source. If you spot an inaccuracy, let me know via the contact form.
AI Summary

The case concerns DigiCert’s handling of two EV leaf certificates whose serialNumber values were reported as incorrect. An external reporter contacted DigiCert on 13 June 2020 to revoke the two certificates, citing that there was no organisation linked to the serialNumber value “BG” and referencing a misissuance report. DigiCert initially stated on 17 June 2020 that the certificates had not been misissued and that they would not be revoked. After further clarification and discussion, DigiCert later indicated that the certificates would be revoked, stating the revocation would occur 5 days after DigiCert received updated registration information from the registering authority on 21 June 2020 10:27 MDT, which DigiCert noted would surpass the 5-day mandated revocation timeline in section 4.9.1.1. The reporter subsequently confirmed on 20 June 2020 that the issue appeared resolved after DigiCert clarified that “BG” was assigned as the registration number by the Office of the Superintendent of Financial Institutions. The bug was resolved as INVALID.

Model: gpt-5.4-nano Generated: 2026-06-13 11:37 UTC Revised: 2026-06-16 19:03 UTC Confidence: 0.86 5 comments
Chronology
  1. An external reporter notified DigiCert to revoke two EV leaf certificates due to an alleged serialNumber discrepancy.
  2. DigiCert stated it was not planning to revoke the certificates.
  3. DigiCert received updated registration information from the registering authority (as stated in the thread).
  4. The reporter confirmed the issue appeared resolved after DigiCert clarified the meaning of “BG”.
Thread Activity
  1. Fozzie representative — Reported that DigiCert failed to revoke two invalid serialNumber EV certificates within 5 days and provided a timeline including DigiCert’s initial refusal to revoke and later statement about revocation after receiving new registration information.
  2. DigiCert — Said DigiCert was not planning revocation because the certificates were properly issued and that the earlier claim about receiving a new incorporation number was incorrect.
  3. Fozzie representative — Asked for clarification on what documents DigiCert had that linked “BG” to the company.
  4. DigiCert — Clarified that “BG” was assigned as the registration number by the Office of the Superintendent of Financial Institutions.
  5. Fozzie representative — Acknowledged the clarification and stated the issue seemed resolved.
Participants
Fozzie representative DigiCert
Similar Local Cases
#1639801 RESOLVED Delayed Revocation Opened 2020-05-21 · Closed 2023-02-22 · 97% similar
DigiCert: Failure to revoke key-compromised certificates within 24 hours
#1516599 RESOLVED Delayed Revocation Opened 2018-12-28 · Closed 2023-02-22 · 96% similar
DigiCert: Underscores - Ericsson
#1639802 RESOLVED Delayed Revocation Opened 2020-05-21 · Closed 2023-02-22 · 96% similar
DigiCert: Failure to revoke key-compromised certificate
#1516453 RESOLVED Delayed Revocation Opened 2018-12-26 · Closed 2023-02-22 · 95% similar
DigiCert: Underscores - Discover
#1516561 RESOLVED Delayed Revocation Opened 2018-12-27 · Closed 2023-02-22 · 95% similar
DigiCert: Underscores - Canadian Imperial Bank of Commerce
#1517617 RESOLVED Delayed Revocation Opened 2019-01-03 · Closed 2023-02-22 · 95% similar
DigiCert: Underscores - Citi
#1651828 RESOLVED Delayed Revocation Opened 2020-07-09 · Closed 2023-02-22 · 93% similar
DigiCert: Delay of revocation for EV audit inconsistency incident
#1653475 RESOLVED Delayed Revocation Opened 2020-07-17 · Closed 2023-02-22 · 90% similar
DigiCert: Key Size Not Divisible By 8

We use only essential cookies and local browser storage for preferences and security. See our Privacy Policy for details.

Confirm action