← Asseco Data Systems S.A. cases
Bugzilla #1853663 Certificate Misissuance

Asseco DS / Certum: S/MIME certificates issued with incorrect organizationIdentifier

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 that it identified S/MIME certificates that were issued with an incorrect organizationIdentifier. The CA said it first became aware of the issue on September 17, 2023, when its Certum Validation Team found two incorrectly issued certificates during a routine check. The CA stated that it immediately revoked the two affected certificates and informed customers so they could submit new certificate requests. The CA reported that the misissuance was caused by a combination of factors, including a validator that could alert but did not prevent issuance, and a Validation Officer misunderstanding instructions related to using EUID versus the intended fields in the organizationIdentifier. The CA also reported additional training for the Validation Team and planned an additional validator to block issuance when organizationIdentifier errors are detected. The CA later confirmed that no further misissuance had occurred and that the analysis found no more errors. The bug was resolved as FIXED and Mozilla indicated it would close it on or about October 18, 2023 unless there were community questions.

Model: gpt-5.4-nano Generated: 2026-06-13 21:32 UTC Revised: 2026-06-16 18:10 UTC Confidence: 0.86 5 comments
Chronology
  1. Certum Validation Team identified two S/MIME certificates with incorrect organizationIdentifier during a routine check.
  2. The CA revoked the two affected certificates and enabled customers to request corrected replacements.
  3. Compliance began analysis to determine whether additional incorrectly issued certificates existed.
  4. Additional training was conducted for the Validation Team regarding organizationIdentifier.
  5. The CA completed its analysis and reported no further errors.
  6. Mozilla indicated it would close the bug on or about 18-Oct-2023 unless there were community questions.
Thread Activity
  1. Assecods representative — Reported that on September 17 the Validation Team informed the CA about several S/MIME certificates with incorrect OrganizationIdentifier, identified two issued certificates, and stated they were immediately revoked with customer notification; promised a detailed report by September 29, 2023.
  2. Assecods representative — Provided a detailed incident timeline, described the causes (validator signaling but not preventing issuance and misunderstanding of EUID usage), listed affected certificate serial numbers, and described remediation steps including training and a planned blocking validator.
  3. Assecods representative — Stated there were no additional updates for the bug.
  4. Assecods representative — Confirmed no new misissuance had occurred and asked whether the bug could be closed.
  5. Mozilla representative — Said Mozilla would close the bug on or about 18-Oct-2023 unless there were questions from the community.
Participants
Assecods representative Mozilla representative
External References
Similar Local Cases
#1823040 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2023-03-17 · Closed 2023-05-19 · 89% similar
Asseco DS / Certum: Cross-certificate with wrong policy identifier
#1550575 RESOLVED Certificate Misissuance Opened 2019-05-09 · Closed 2023-02-22 · 83% similar
Asseco DS / Certum: commonName not from subjectAltName entries
#1420860 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2017-11-27 · Closed 2023-02-22 · 81% similar
Asseco DS / Certum: CAA Mis-Issuance on mix of wildcard and non-wildcard DNS names in SAN
#1600301 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2019-11-29 · Closed 2023-02-22 · 81% similar
Asseco DS / Certum: EV Certificates issued with wrong Business Category
#1409764 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2017-10-18 · Closed 2023-02-22 · 80% similar
Asseco DS / Certum: CAA mis-issuance on critical flag and unknown CAA tag
#1709392 RESOLVED Self Reported Incident Certificate Misissuance Opened 2021-05-04 · Closed 2023-02-22 · 77% similar
Asseco DS / Certum: Invalid stateOrProvinceName field (recurrent incident)
#1711208 RESOLVED Self Reported Incident Certificate Misissuance Opened 2021-05-14 · Closed 2023-02-22 · 77% similar
Asseco DS / Certum: Incorrect localityName
#1865080 RESOLVED Certificate Misissuance Opened 2023-11-16 · Closed 2024-01-04 · 76% similar
Asseco DS / Certum: TLS EV certificates with incorrect Subject attribute order

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

Confirm action