← Government of Turkey, Kamu Sertifikasyon Merkezi (Kamu SM) cases
Bugzilla #1847193 Certificate Misissuance

KAMU SM: commonName not in SAN

RESOLVED FIXED Government of Turkey, Kamu Sertifikasyon Merkezi (Kamu SM)
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

KAMU SM identified a compliance issue where a certificate was issued without the commonName (CN) field included in the Subject Alternative Name (SAN) extension. Upon discovery on August 4, 2023, the affected certificate was revoked immediately. The CA conducted a thorough investigation, confirming that the misissuance was due to human error during the certificate issuance process. KAMU SM implemented additional controls in their checklist to prevent similar incidents and has since integrated pre-issuance linting into their certificate management infrastructure. As of September 27, 2023, all remediation actions have been completed, and the incident is now resolved.

Model: gpt-4o-mini Generated: 2026-06-13 21:11 UTC Revised: 2026-06-16 19:11 UTC Confidence: 0.90 13 comments
Chronology
  1. KAMU SM discovered a certificate was issued without a CN field in the SAN extension.
  2. Pre-issuance linting and other remediation measures became operational.
Thread Activity
  1. Tubitak representative — Kamu SM discovered that a certificate was issued without a CN field in the SAN extension. The affected certificate was revoked immediately.
  2. Tubitak representative — KAMU SM provided a detailed timeline of actions taken in response to the misissuance.
  3. Tubitak representative — KAMU SM updated their checklist to include additional controls.
  4. Tubitak representative — KAMU SM confirmed that pre-issuance linting is operational in the production environment.
Participants
Tubitak representative Binaryparadox representative Mozilla representative
External References
Similar Local Cases
#1551369 RESOLVED Self Reported Incident Certificate Misissuance Opened 2019-05-14 · Closed 2023-02-22 · 82% similar
Kamu SM: "Some-State" in stateOrProvinceName
#1390998 RESOLVED Self Reported Incident Certificate Misissuance Opened 2017-08-16 · Closed 2023-02-22 · 80% similar
Kamu SM: Non-BR-Compliant Certificate Issuance
#1986968 RESOLVED Ca Certificate Compliance Certificate Misissuance Closure Request Opened 2025-09-04 · Closed 2026-04-06 · 75% similar
Financijska agencija (Fina): Mis-issued certificates
#1716123 RESOLVED Ca Certificate Compliance Certificate Misissuance Self Reported Incident Opened 2021-06-12 · Closed 2024-05-25 · 75% similar
e-commerce monitoring GmbH: CN domain not in SAN
#1731586 RESOLVED Ca Certificate Compliance Self Reported Incident Certificate Misissuance Opened 2021-09-20 · Closed 2023-02-22 · 73% similar
SwissSign: Certificate with key length 16258
#1921254 RESOLVED Certificate Misissuance Self Reported Incident Opened 2024-09-26 · Closed 2025-02-19 · 73% similar
Izenpe: Duplicate attribute in Subject
#1674886 RESOLVED Certificate Misissuance Opened 2020-11-02 · Closed 2023-02-22 · 73% similar
certSIGN: misissued an OV SSL certificate with no organizationName and localityName, instead of a DV SSL as requested by client
#1936908 RESOLVED Certificate Misissuance Opened 2024-12-12 · Closed 2025-03-18 · 72% similar
DigiCert: Encoded HTML entities in attribute values

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

Confirm action