← Asseco Data Systems S.A. cases
Bugzilla #2071348 Ca Certificate Compliance Externally Reported Incident Certificate Misissuance Revocation Issue Remediation Tracking

Certum EV TLS certificates issued with branch name in subject organizationName

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

Certum reported a third-party-identified incident involving two EV TLS certificates issued for organizations registered in Hong Kong. In each case, the certificate’s subject organizationName contained a branch name, while the subject serialNumber referred to the parent corporation’s registration number. Certum said the validation records did not establish that the branches were legally recognized entities distinct from their parent corporations, and the parent corporation’s full legal name was not included in subject organizationName. Certum investigated the validation process, reviewed other Hong Kong EV TLS and EV Code Signing requests, and stopped one similar pending request before issuance. Both affected certificates were revoked, and Certum updated its Hong Kong validation instructions and training before requesting closure.

Model: gpt-5.4-mini Generated: 2026-10-20 17:32 UTC Confidence: 0.97 8 comments
Chronology
  1. Certum issued the first affected EV TLS certificate after validating the request.
  2. Certum issued the second affected EV TLS certificate after validating the request.
  3. Certum received a Certificate Problem Report about one affected certificate and began investigating.
  4. Certum revoked the first affected certificate.
  5. Certum revoked the second affected certificate.
  6. Certum incorporated clarification from the Hong Kong business registration authority into revised validation instructions.
Thread Activity
  1. Assecods representative — Certum filed a preliminary incident report saying a third party reported the issue and that scope review was ongoing.
  2. Assecods representative — Certum filed the full incident report, described the two affected certificates, and said one similar pending request had been stopped before issuance.
  3. Assecods representative — Certum updated the action items and marked the remediation tasks complete.
  4. Assecods representative — Certum posted the closure summary and requested closure of the incident report.
  5. CCADB representative — CCADB issued a final call for comments and said the bug would be closed if no further questions were raised.
Participants
Assecods representative CCADB representative
Related Bugzilla IDs Mentioned
Similar Local Cases
#2061178 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Externally Reported Incident Opened 2026-08-06 · Closed 2026-10-02 · 96% similar
Asseco DS / Certum: Incorrect Country in certificate
#2044023 RESOLVED Certificate Misissuance Self Reported Incident Remediation Tracking Opened By Ca Opened 2026-06-01 · Closed 2026-07-02 · 89% similar
Asseco DS / Certum: Cross-Certificates subject encoding discrepancy
#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
#2058918 ASSIGNED Ca Certificate Compliance Externally Reported Incident Certificate Misissuance Validation Issue Opened 2026-07-29 Still Open · 79% similar
CFCA: Incorrect countryName values in OV subscriber certificates
#1420860 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2017-11-27 · Closed 2023-02-22 · 79% similar
Asseco DS / Certum: CAA Mis-Issuance on mix of wildcard and non-wildcard DNS names in SAN
#2062100 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Certificate Misissuance Opened 2026-08-10 · Closed 2026-09-17 · 78% similar
DigiCert: jurisdictionCountry in EV certificate
#2056087 RESOLVED Ca Certificate Compliance Incident Externally Reported Incident Certificate Misissuance Opened 2026-07-19 · Closed 2026-09-14 · 78% similar
Disig: CP/CPS misstatement regarding Key Usage criticality for TLS certificates
#2032473 RESOLVED Ca Certificate Compliance Incident Externally Reported Incident Certificate Misissuance Opened 2026-04-16 · Closed 2026-08-08 · 78% similar
CCA India: Misissuance detected by PKIMetal

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

⚠

Confirm action