← Asseco Data Systems S.A. cases
Bugzilla #1709392 Self Reported Incident Certificate Misissuance

Asseco DS / Certum: Invalid stateOrProvinceName field (recurrent incident)

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

Asseco Data Systems S.A. (Certum) reported a recurrent issue regarding the invalid 'stateOrProvinceName' field in several certificates. The problem was initially identified by a third party on May 4, 2021, prompting Certum to conduct a thorough analysis and implement corrective measures. They discovered multiple certificates with incorrect values and initiated revocation procedures. By May 12, 2021, five certificates were revoked, and further analysis revealed additional errors, leading to the revocation of 23 more certificates by May 15, 2021. Certum has committed to improving its validation processes to prevent future occurrences.

Model: gpt-4o-mini Generated: 2026-06-13 21:25 UTC Revised: 2026-06-16 18:08 UTC Confidence: 0.85 19 comments
Chronology
  1. Certum received a report from a third party about incorrect stateOrProvinceName values in issued certificates.
  2. Certum revoked five certificates with invalid stateOrProvinceName values.
  3. Certum revoked an additional 23 certificates identified with errors in the stateOrProvinceName field.
Thread Activity
  1. Fozzie representative — Reported multiple certificates with invalid stateOrProvinceNames, indicating a recurrent issue.
  2. Assecods representative — Acknowledged the report and stated that an incident report would be forthcoming.
  3. Assecods representative — Provided a detailed timeline of actions taken in response to the issue.
  4. Assecods representative — Confirmed the revocation of five certificates with invalid stateOrProvinceName.
  5. Assecods representative — Reported the revocation of an additional 23 certificates with errors.
Participants
Fozzie representative Assecods representative Community commenter Lebihan representative Asseco Data Systems S.A. Mozilla representative
External References
Related Bugzilla IDs Mentioned
Similar Local Cases
#1409766 RESOLVED Ca Certificate Compliance Self Reported Incident Certificate Misissuance Opened 2017-10-18 · Closed 2023-02-22 · 100% similar
Asseco DS / Certum: CAA Mis-Issuance on CNAME pointing directly to restrictive CAA record
#1639502 RESOLVED Self Reported Incident Opened 2020-05-20 · Closed 2023-02-22 · 100% similar
Asseco DS / Certum: Incorrect OCSP response encoding
#1667684 RESOLVED Self Reported Incident Opened 2020-09-27 · Closed 2023-02-22 · 100% similar
Asseco DS / Certum: Failure to provide a preliminary report within 24 hours.
#1711208 RESOLVED Self Reported Incident Certificate Misissuance Opened 2021-05-14 · Closed 2023-02-22 · 100% similar
Asseco DS / Certum: Incorrect localityName
#1832093 RESOLVED Self Reported Incident Certificate Misissuance Opened 2023-05-09 · Closed 2023-06-02 · 100% similar
Asseco DS / Certum: Subordinate certificates with sequential serial number
#1708834 RESOLVED Certificate Misissuance Self Reported Incident Opened 2021-04-30 · Closed 2023-02-22 · 99% similar
GlobalSign: Invalid stateOrProvinceName and locality pair
#1865080 RESOLVED Certificate Misissuance Opened 2023-11-16 · Closed 2024-01-04 · 97% similar
Asseco DS / Certum: TLS EV certificates with incorrect Subject attribute order
#1917571 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2024-09-09 · Closed 2024-11-06 · 97% similar
Asseco DS / Certum: Organization Identifier and Country field discrepancies

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

Confirm action