← Asseco Data Systems S.A. cases
Bugzilla #1871393 Delayed Revocation

Asseco DS / Certum: Delayed revocation of EV certificates

RESOLVED FIXED Asseco Data Systems S.A.
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

This case concerns Certum (Asseco Data Systems S.A.) issuing 138 EV TLS certificates with an incorrect relative order of Subject attributes after September 15, 2023. The incident was linked to a prior bug (1865080) showing that the certificates were not revoked within the time specified by the CA/B Forum Baseline Requirements. Certum reported that it revoked all affected certificates on November 21, 2023, and provided a timeline and root cause analysis for the revocation delay. In its analysis, Certum stated it had misunderstood the revocation deadline by counting full days rather than distinguishing hours versus days, which it said led to the delay. The bug was created to clarify the situation, and Certum also stated it would change internal instructions from “5 days” to “120 hours” for revocation. The bug is marked RESOLVED with resolution FIXED, and Mozilla indicated it would be closed on 29-Dec-2023 unless further discussion was needed.

Model: gpt-5.4-nano Generated: 2026-06-13 21:33 UTC Revised: 2026-06-16 18:11 UTC Confidence: 0.90 3 comments
Chronology
  1. Certum began issuing EV TLS certificates with an incorrect relative order of Subject attributes.
  2. Certum revoked all affected EV TLS certificates.
  3. Mozilla closed the loop on the bug after discussion, with no further updates expected.
Thread Activity
  1. Assecods representative — Created an incident report attachment describing 138 affected EV TLS certificates, the revocation timeline, root cause analysis for the delayed revocation, and an action item to change internal revocation instructions from 5 days to 120 hours.
  2. Mozilla representative — Stated the bug would be closed on 29-Dec-2023 unless further discussion was needed.
  3. Assecods representative — Confirmed there were no additional updates for the bug.
Participants
Assecods representative Mozilla representative
External References
Related Bugzilla IDs Mentioned
Similar Local Cases
#1667986 RESOLVED Delayed Revocation Opened 2020-09-29 · Closed 2023-02-22 · 99% similar
Asseco DS / Certum: Invalid stateOrProvinceName field
#1825734 RESOLVED Delayed Revocation Opened 2023-03-31 · Closed 2023-06-01 · 98% similar
Asseco DS / Certum: Delayed revocation of SHECA cross certificate
#1826363 RESOLVED Delayed Revocation Opened 2023-04-04 · Closed 2023-06-08 · 97% similar
Asseco DS / Certum: Delayed revocation of SSL.COM cross certificate
#1668523 RESOLVED Delayed Revocation Revocation Issue Opened 2020-10-01 · Closed 2023-02-22 · 95% similar
Asseco DS / Certum: Failure to revoke within 5 days
#2023190 RESOLVED Delayed Revocation Opened 2026-03-13 · Closed 2026-04-19 · 88% similar
Asseco DS / Certum: Delayed revocation of S/MIME certificates issued with mailbox validation older than 30 days
#1600158 RESOLVED Ca Certificate Compliance Delayed Revocation Opened 2019-11-28 · Closed 2023-02-22 · 83% similar
Asseco DS / Certum: Failure to revoke intermediate certificates within the BR time period
#1524195 RESOLVED Certificate Misissuance Delayed Revocation Opened 2019-01-31 · Closed 2023-02-22 · 81% similar
Asseco DS / Certum: Invalid dnsNames
#1826363 RESOLVED Delayed Revocation Opened 2023-04-04 · Closed 2023-06-08 · 79% similar
Asseco DS / Certum: Delayed revocation of SSL.COM cross certificate

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

Confirm action