← DigiCert cases
Bugzilla #2083502
Ca Certificate Compliance
Incident
Self Reported Incident
Linting Quality Issue
DigiCert preliminary incident report: CRLNumber sequence not strictly increasing within one CRL scope
UNCONFIRMED
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
DigiCert opened this bug as a preliminary incident report after a third party reported an issue with two DigiCert Issuing CA CRLs disclosed in CCADB. The report says the CRLs have the same scope and issuer and share one cRLNumber sequence. It also says that, in several observed instances, the cRLNumber decreased between versions, which the report notes is inconsistent with BR Section 7.2.2 and RFC 5280 Section 5.2.3. The thread provided here does not include any remediation, resolution, or follow-up beyond the initial disclosure. The case is therefore a self-disclosed compliance incident about CRLNumber sequencing.
Chronology
- A third party reported that two CRLs for the same DigiCert Issuing CA scope and issuer shared one cRLNumber sequence and showed decreases between versions.
Thread Activity
- DigiCert — DigiCert filed a preliminary incident report describing the CRLNumber sequencing issue and citing BR Section 7.2.2 and RFC 5280 Section 5.2.3.
Participants
DigiCert
External References
Similar Local Cases
DigiCert: Certificates issued for sanctioned entities
DigiCert: Several non-functioning AIA URLs
DigiCert: Threat of legal action to stifle Bugzilla discourse
DigiCert: Misissued code signing certificates
DigiCert: OCSP NextUpdate
DigiCert / Microsoft: inconsistent disclosure of externally-operated intermediate
DigiCert: Failure to provide a preliminary report within 24 hours.
DigiCert: Invalid stateOrProvinceName