Asseco DS / Certum: Failure to provide a preliminary report within 24 hours.

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

This case involves Asseco Data Systems S.A. (Certum) failing to provide a preliminary report within the required 24-hour timeframe after receiving a Certificate Problem Report. The issue was triggered by a report concerning the incorrect issuance of certificates with an invalid stateOrProvinceName field. Certum acknowledged the delay in their response and provided a timeline of events leading to the oversight. They have since updated their procedures to ensure compliance with the Baseline Requirements. The case has been resolved with the implementation of these corrective measures.

Model: gpt-4o-mini Generated: 2026-06-13 21:23 UTC Revised: 2026-06-16 18:07 UTC Confidence: 0.85 17 comments

Chronology

2020-09-26 Certum received a report about incorrect certificate issuance.
2020-09-28 Certum acknowledged the failure to respond within the required timeframe.
2020-10-01 Certum updated their procedures to ensure timely responses.
2020-11-13 The bug was resolved and closed.

Thread Activity

2020-09-27 Fozzie representative — Reported a lack of response from Certum regarding a certificate issue.
2020-09-28 Assecods representative — Certum acknowledged the incident report and began analysis.
2020-10-01 Assecods representative — Certum provided details on updated procedures for handling reports.
2020-11-13 Assecods representative — Confirmed no further questions and requested to close the bug.

Participants

Fozzie representative Assecods representative Asseco Data Systems S.A. Community commenter Mozilla representative

External References

Original Bugzilla Case bugzilla.mozilla.org

Similar Local Cases

#1639502 RESOLVED Self Reported Incident Opened 2020-05-20 · Closed 2023-02-22 · 100% similar

Asseco DS / Certum: Incorrect OCSP response encoding

AI Summary CA Owner

#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)

AI Summary CA Owner

#1711208 RESOLVED Self Reported Incident Certificate Misissuance Opened 2021-05-14 · Closed 2023-02-22 · 100% similar

Asseco DS / Certum: Incorrect localityName

AI Summary CA Owner

#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

AI Summary CA Owner

#1815355 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2023-02-07 · Closed 2023-08-16 · 98% similar

Asseco DS / Certum: Cross-Signed non-EV-audited root with an EV-enabled root

AI Summary CA Owner

#1832093 RESOLVED Self Reported Incident Certificate Misissuance Opened 2023-05-09 · Closed 2023-06-02 · 95% similar

Asseco DS / Certum: Subordinate certificates with sequential serial number

AI Summary CA Owner

#1649277 RESOLVED Self Reported Incident Incident Opened 2020-06-29 · Closed 2023-02-22 · 90% similar

DigiCert: Failure to provide a preliminary report within 24 hours.

AI Summary CA Owner

#1708834 RESOLVED Certificate Misissuance Self Reported Incident Opened 2021-04-30 · Closed 2023-02-22 · 87% similar

GlobalSign: Invalid stateOrProvinceName and locality pair

AI Summary CA Owner