← Deutsche Telekom Security GmbH cases
Bugzilla #2080708 Ca Certificate Compliance Incident Externally Reported Incident Vulnerability Disclosure

Telekom Security preliminary incident report: OCSP responder used incorrect signature algorithm for P-384 signing key

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

Deutsche Telekom Security GmbH opened this case after receiving a Certificate Problem Report about its OCSP responder producing non-compliant OCSP responses. The report said the responder used an incorrect signature algorithm for a P-384 signing key, contrary to the Baseline Requirements requirement that P-384 signatures use ECDSA with SHA-384 and a specific AlgorithmIdentifier encoding. The incident was disclosed as third-party reported, not self-discovered. Telekom Security filed a preliminary incident report and said it needed more time to complete the full incident report. It stated that the full report would be provided no later than 2026-10-23.

Model: gpt-5.4-mini Generated: 2026-10-20 17:37 UTC Confidence: 0.97 2 comments
Chronology
  1. A Certificate Problem Report was received about non-compliant OCSP responses using an incorrect signature algorithm for a P-384 signing key.
  2. Telekom Security opened a preliminary incident report describing the OCSP responder issue.
  3. Telekom Security said it would provide the full incident report by this date.
Thread Activity
  1. Telekom representative — Reported that the OCSP responder used an incorrect signature algorithm for a P-384 signing key and identified the case as third-party reported.
  2. Telekom representative — Said more time was needed to complete the full incident report and promised it by 2026-10-23.
Participants
Telekom representative
External References
Similar Local Cases
#2082799 NEW Ca Certificate Compliance Policy Document Issue Incident Externally Reported Incident Opened 2026-10-16 Still Open · 91% similar
Telekom Security: Typographical error in CPS section 7.1.6
#2004668 RESOLVED Ca Certificate Compliance Opened 2025-12-08 · Closed 2026-01-20 · 79% similar
Telekom Security: Root-CA certificates published in PEM encoded format
#2077068 ASSIGNED Ca Certificate Compliance Incident Externally Reported Incident Revocation Issue Opened 2026-10-01 Still Open · 78% similar
Telekom Security: Failure in automatic issuance of CRLs
#2076163 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Problem Reporting Failure Opened 2026-09-28 Still Open · 77% similar
Telekom Security: Failure to respond to a certificate problem report within 24 hours
#2080742 ASSIGNED Ca Certificate Compliance Externally Reported Incident Certificate Misissuance Information Request Opened 2026-10-12 Still Open · 75% similar
eMudhra emSign PKI Services: Delegated OCSP Responder certificates containing cRLDistributionPoints extension
#2080806 ASSIGNED Ca Certificate Compliance Externally Reported Incident Incident Vulnerability Disclosure Opened 2026-10-12 Still Open · 73% similar
Actalis: Non-compliant OCSP responses and OCSP responder certificate
#2080229 ASSIGNED Ca Certificate Compliance Externally Reported Incident Incident Vulnerability Disclosure Opened 2026-10-09 Still Open · 72% similar
NAVER Cloud Trust Services: OCSP responses with an empty responseExtensions
#2075255 ASSIGNED Ca Certificate Compliance Externally Reported Incident Problem Reporting Failure Opened 2026-09-24 Still Open · 72% similar
NETLOCK: Certificate Problem Report [CRL BR S7.2.2]

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

⚠

Confirm action