← Deutsche Telekom Security GmbH cases
Bugzilla #2076096 Ca Certificate Compliance Incident Externally Reported Incident Repository Issue

Telekom Security / DFN: CRL crlEntryExtensions zero-length SEQUENCE non-compliance

ASSIGNED Deutsche Telekom Security GmbH
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 a CRL non-compliance in the DFN-operated hierarchy under Telekom Security’s root. The incident report says CRLs issued by DFN contained a zero-length crlEntryExtensions SEQUENCE in revokedCertificates entries when no reason code was present, which violates RFC 5280. The issue was third-party reported, and the full incident report states that issuance for the affected PKI hierarchy had already stopped on 2023-08-31 because the hierarchy will be discontinued. Telekom Security said DFN would submit the full incident report because the non-compliance originated from an externally operated sub-CA, while Telekom Security remained responsible as root CA and continued working with DFN. The thread later recorded remediation action items, including creating a software fix, publishing a compliant CRL, and checking for similar errors, all of which were marked completed by 2026-10-20.

Model: gpt-5.4-mini Generated: 2026-10-20 17:37 UTC Confidence: 0.96 5 comments
Chronology
  1. DFN’s CRL generation process began producing revokedCertificates entries with zero-length crlEntryExtensions when no reason code was given.
  2. Issuance for the affected PKI hierarchy stopped.
  3. A certificate problem report was sent to Telekom Security about the CRL issue.
  4. DFN submitted the full incident report describing the RFC 5280 non-compliance.
  5. DFN reported completion of the remaining action item and said no similar errors were found.
Thread Activity
  1. Telekom representative — Opened a preliminary incident report describing the zero-length crlEntryExtensions issue and noting it was third-party reported.
  2. Telekom representative — Explained that DFN would submit the full incident report because the non-compliance originated from an externally operated sub-CA, while Telekom Security remained responsible as root CA.
  3. Dfn-cert representative — Submitted the full incident report, including timeline, impact, related incidents, and root cause analysis.
  4. Dfn-cert representative — Requested the Next Update field be set to 2026-10-23 for the remaining open action item.
  5. Dfn-cert representative — Reported completion of the remaining action item and listed all action items as completed.
Participants
Telekom representative Dfn-cert representative
Related Bugzilla IDs Mentioned
Similar Local Cases
#2077068 ASSIGNED Ca Certificate Compliance Incident Externally Reported Incident Revocation Issue Opened 2026-10-01 Still Open · 90% similar
Telekom Security: Failure in automatic issuance of CRLs
#2083715 NEW Ca Certificate Compliance Incident Externally Reported Incident Policy Document Issue Opened 2026-10-19 Still Open · 88% similar
Telekom Security / DFN: CRL validity period exceeds 10 days by one second
#2076163 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Problem Reporting Failure Opened 2026-09-28 Still Open · 87% similar
Telekom Security: Failure to respond to a certificate problem report within 24 hours
#2074944 ASSIGNED Ca Certificate Compliance Incident Externally Reported Incident Ccadb Disclosure Issue Opened 2026-09-23 Still Open · 72% similar
Let's Encrypt: Root CRLs Missing Reason Code
#2080698 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Ccadb Disclosure Issue Opened 2026-10-12 Still Open · 71% similar
Certigna: Failure to announce completion of action item within prescribed time period
#2066068 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Problem Reporting Failure Opened 2026-08-24 Still Open · 71% similar
SECOM: Missing Prior Notification and Approval for a Cross-Certificate Extending Trust to Externally-Operated JPRS CAs
#2058261 ASSIGNED Ca Documents Incident Self Reported Incident Policy Document Issue Opened 2026-07-27 Still Open · 71% similar
Google Trust Services: CPS Missing root program attestation
#2056934 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Problem Reporting Failure Opened 2026-07-22 · Closed 2026-10-05 · 71% similar
Actalis: failure to timely update CP/CPS for AgID SubCAs

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

⚠

Confirm action