← Asseco Data Systems S.A. cases
Bugzilla #1832093 Self Reported Incident Certificate Misissuance

Asseco Data Systems / Certum: Subordinate certificates with sequential serial number

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

Asseco Data Systems S.A. / Certum reported a compliance issue discovered during its periodic self-audit: it found that the serial numbers of subordinate certificates were sequential, which it suspected was generated with insufficient entropy. The CA confirmed that two subordinate certificates had sequential serial numbers and disclosed the findings in this bug, then performed a detailed investigation to identify the root cause. The CA revoked the first subordinate certificate identified in the initial finding and later identified and confirmed the reason for the sequential serial numbers. It implemented a fix for the software used to generate subordinate certificates, expanded tests for CA certificates, and revoked the second subordinate certificate from the initial finding. During a comprehensive scan, the CA found a third subordinate certificate with a sequential serial number and scheduled its revocation; it later stated that the third certificate was revoked as scheduled. The CA also updated its systems to prevent additional issuance of CA certificates with a sequential serial number, and the bug was resolved as FIXED.

Model: gpt-5.4-nano Generated: 2026-06-13 21:31 UTC Revised: 2026-06-16 18:10 UTC Confidence: 0.90 7 comments
Chronology
  1. During a periodic self-audit, the CA detected subordinate certificates with sequential serial numbers and suspected insufficient entropy in serial generation.
  2. The CA began a detailed investigation and revoked the first identified subordinate certificate.
  3. The CA implemented a fix for subordinate certificate serial generation software and expanded tests for CA certificates.
  4. The CA revoked the second identified subordinate certificate and completed a review that found no other affected CA certificates; it also identified a third affected subordinate certificate.
  5. The CA revoked the third subordinate certificate as scheduled.
  6. The bug was resolved as FIXED.
Thread Activity
  1. Asseco Data Systems S.A. — Reported that the CA’s periodic self-audit detected sequential serial numbers in subordinate certificates and said it would provide a full incident report within 7 days.
  2. Asseco Data Systems S.A. — Provided a detailed timeline and stated that two subordinate certificates were confirmed to have sequential serial numbers, with subsequent investigation and revocations planned.
  3. Asseco Data Systems S.A. — Confirmed that the specified certificate on crt.sh was revoked as scheduled.
  4. Thisisntrocket representative — Noted that one certificate showed "good" on OCSP while the other linked certificates showed "Revoked (superseded)".
  5. Asseco Data Systems S.A. — Said the CA verified OCSP status after updating its database and that crt.sh OCSP validator appeared to have delayed status updates, now showing revoked.
  6. Asseco Data Systems S.A. — Stated there were no further updates.
  7. Mozilla representative — Indicated Mozilla intended to close the bug on or about 2-June-2023 unless there were concerns.
Participants
Asseco Data Systems S.A. Thisisntrocket representative Mozilla representative
Similar Local Cases
#1709392 RESOLVED Self Reported Incident Certificate Misissuance Opened 2021-05-04 · Closed 2023-02-22 · 100% similar
Asseco DS / Certum: Invalid stateOrProvinceName field (recurrent incident)
#1409766 RESOLVED Ca Certificate Compliance Self Reported Incident Certificate Misissuance Opened 2017-10-18 · Closed 2023-02-22 · 99% similar
Asseco DS / Certum: CAA Mis-Issuance on CNAME pointing directly to restrictive CAA record
#1711208 RESOLVED Self Reported Incident Certificate Misissuance Opened 2021-05-14 · Closed 2023-02-22 · 99% similar
Asseco DS / Certum: Incorrect localityName
#1639502 RESOLVED Self Reported Incident Opened 2020-05-20 · Closed 2023-02-22 · 97% similar
Asseco DS / Certum: Incorrect OCSP response encoding
#1917571 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2024-09-09 · Closed 2024-11-06 · 97% similar
Asseco DS / Certum: Organization Identifier and Country field discrepancies
#1667684 RESOLVED Self Reported Incident Opened 2020-09-27 · Closed 2023-02-22 · 95% similar
Asseco DS / Certum: Failure to provide a preliminary report within 24 hours.
#1511459 RESOLVED Self Reported Incident Opened 2018-11-30 · Closed 2023-02-22 · 88% similar
Asseco DS / Certum: Corrupted certificates
#1865080 RESOLVED Certificate Misissuance Opened 2023-11-16 · Closed 2024-01-04 · 88% similar
Asseco DS / Certum: TLS EV certificates with incorrect Subject attribute order

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

Confirm action