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

Asseco DS / Certum: Incorrect localityName

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. identified three certificates with an incorrect localityName field while analyzing a related bug. The CA discovered the issue on May 14, 2021, and subsequently revoked the affected certificates by June 16, 2021. They implemented additional checks for localityName as part of their address validation process and are developing automated verification methods to prevent future errors. The CA has confirmed that they have ceased issuing certificates with this problem and are actively working on improving their verification processes.

Model: gpt-4o-mini Generated: 2026-06-13 21:27 UTC Revised: 2026-06-16 18:08 UTC Confidence: 0.85 12 comments
Chronology
  1. Asseco DS discovered three certificates with an incorrect localityName.
  2. All identified certificates were revoked.
Thread Activity
  1. Assecods representative — Found 3 certificates with an invalid localityName field.
  2. Assecods representative — Completed analysis and found an additional 16 certificates with errors.
  3. Assecods representative — All certificates mentioned were revoked.
  4. Mozilla representative — Scheduled for closure unless there are further questions.
Participants
Assecods representative Fozzie representative Community commenter Mozilla representative
External References
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
#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.
#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)
#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
#1832093 RESOLVED Self Reported Incident Certificate Misissuance Opened 2023-05-09 · Closed 2023-06-02 · 99% similar
Asseco DS / Certum: Subordinate certificates with sequential serial number
#1865080 RESOLVED Certificate Misissuance Opened 2023-11-16 · Closed 2024-01-04 · 98% similar
Asseco DS / Certum: TLS EV certificates with incorrect Subject attribute order
#1815355 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2023-02-07 · Closed 2023-08-16 · 97% similar
Asseco DS / Certum: Cross-Signed non-EV-audited root with an EV-enabled root
#1708834 RESOLVED Certificate Misissuance Self Reported Incident Opened 2021-04-30 · Closed 2023-02-22 · 95% similar
GlobalSign: Invalid stateOrProvinceName and locality pair

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

Confirm action