← Asseco Data Systems S.A. cases
Bugzilla #2080819
Problem Reporting Failure
Asseco DS / Certum: Incorrect AlgorithmIdentifier encoding in OCSP responses
ASSIGNED
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 a third-party Certificate Problem Report about incorrect encoding in Certum OCSP responses. The report says that, on 2026-10-09, Certum received notice that the `signatureAlgorithm` field in affected `BasicOCSPResponse` structures omitted the required `NULL` parameters for RSA with SHA-256 and SHA-512. Certum opened a preliminary incident report and said it had started an internal investigation to determine the full scope and root cause. The bug states that a full incident report would be provided no later than 2026-10-23. The thread does not state a final resolution in the provided comments.
Chronology
- Certum received a third-party report about incorrect AlgorithmIdentifier encoding in OCSP responses.
- Certum opened a preliminary incident report in Mozilla Bugzilla.
Thread Activity
- Assecods representative — Reported that Certum received a third-party CPR, described the OCSP encoding issue, and said an internal investigation had begun with a full incident report due by 2026-10-23.
Participants
Assecods representative
External References
Similar Local Cases
TunTrust: OCSP responder "Unknown" of one Pre-certificate
Asseco DS / Certum: Incorrect Country in certificate
Asseco DS / Certum: Delayed publication of Full Incident Report for Bug 2055775
GlobalSign: StateOrProvince and LocalityName value inconsistency
DigiCert: EVG CA profile compliance
Certigna: Pre-certificates not recognised by the OCSP responder
Microsec: Late response to a CPR
Asseco DS / Certum: Incorrect ECDSA-SHA384 AlgorithmIdentifier Encoding in CRLs