← NAVER Cloud Trust Services cases
Bugzilla #1785865 Certificate Misissuance

NAVER Cloud Trust Services: DV certificates issued without Subject Alternative Name (SAN) extension

RESOLVED FIXED NAVER Cloud Trust Services
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

NAVER Cloud Trust Services reported that its NAVER Secure Certification Authority 1 issued 21 DV certificates without the Subject Alternative Name (SAN) extension field for three test domains. The issue was triggered after NAVER Cloud deployed a new internal certificate issuance system (“NAVER Domain Certificate Manager”, NDCM) on 2022-08-18, during which certificates were issued from 11:07 to 13:50 UTC. At 14:26 UTC, NAVER Cloud detected that the SAN extension field value was missing, revoked all 21 affected certificates by 14:29 UTC, and stopped issuing subscriber certificates through NDCM by 14:35 UTC. NAVER Cloud identified a root cause in NDCM: when requesting a certificate from NDCM to the CA engine, the value intended for the SAN extension DNS was sent as a NULL value and the system issued without error. NAVER Cloud then deployed an error-handling hotfix in the CA engine (2022-08-21) and a hotfix in NDCM to modify DNS values (2022-08-22). Later, NAVER Cloud reported completing automated Precertificate Linting in NDCM (test release on 2022-09-22; finished on 2022-10-04) to prevent issuance with warnings or errors, including this type of problem. The bug is marked RESOLVED with resolution FIXED, and Mozilla indicated in 2023-04-07 that there had been no further questions and it was inclined to close it around 2023-04-12.

Model: gpt-5.4-nano Generated: 2026-06-13 20:55 UTC Revised: 2026-06-16 18:33 UTC Confidence: 0.90 8 comments
Chronology
  1. NAVER Cloud deployed NDCM and issued 21 DV certificates missing the SAN extension field for test domains.
  2. NAVER Cloud detected the missing SAN extension, revoked the 21 certificates, and stopped issuing via NDCM.
  3. NAVER Cloud deployed a CA engine hotfix adding error handling for missing SAN extension values.
  4. NAVER Cloud deployed an NDCM hotfix to ensure DNS values are written normally into the SAN extension.
  5. NAVER Cloud completed automated Precertificate Linting in NDCM to prevent issuance with SAN-related warnings or errors.
  6. Mozilla indicated it was inclined to close the incident around 2023-04-12 absent further reasons.
Thread Activity
  1. Navercorp representative — Reported that NAVER Cloud issued 21 DV certificates without SAN extension fields for test domains and revoked them within about 3 hours, and stated a full report would follow.
  2. Thisisntrocket representative — Asked why 21 certificates were issued for what appeared to be three test domains.
  3. Navercorp representative — Provided an incident report describing detection time, revocation, stopping NDCM issuance, root cause (NULL SAN DNS value sent without error), and remediation steps including CA engine and NDCM hotfixes plus certificate listings via crt.sh links.
  4. Mozilla representative — Asked about progress on adding Precertificate Linting to NDCM and testing.
  5. Navercorp representative — Said Precertificate Linting was completed in the test environment on 2022-09-22 and would be released to the real environment the next week.
  6. Navercorp representative — Reported that automated Precertificate Linting was finished on 2022-10-04 and would prevent issuing certificates with warnings or errors, including this bug case.
  7. Navercorp representative — Reported that an internal audit found one additional same-case certificate issued within the past year, revoked immediately, and attributed it to the same root cause with prevention measures already completed.
  8. Mozilla representative — Noted there were no further questions/comments and it was inclined to close the incident around 2023-04-12.
Participants
Navercorp representative Thisisntrocket representative Mozilla representative
Similar Local Cases
#1845269 RESOLVED Certificate Misissuance Incident Opened 2023-07-25 · Closed 2023-09-29 · 80% similar
NAVER Cloud Trust Services: commonName not in SAN
#1866448 RESOLVED Certificate Misissuance Incident Opened 2023-11-24 · Closed 2024-02-14 · 79% similar
NAVER Cloud Trust Services: DV Certificate issued with improperly validated
#1667430 RESOLVED Certificate Misissuance Opened 2020-09-25 · Closed 2023-02-22 · 78% similar
Camerfirma: Invalid stateOrProvinceName field
#1908130 RESOLVED Self Reported Incident Certificate Misissuance Opened 2024-07-16 · Closed 2024-08-28 · 74% similar
NAVER Cloud Trust Services: Incorrect keyUsage for ECC certificate
#1915883 RESOLVED Certificate Misissuance Opened 2024-08-30 · Closed 2024-09-26 · 72% similar
Sectigo: Missing data in cabfOrganizationIdentifier
#1670894 RESOLVED Certificate Misissuance Opened 2020-10-13 · Closed 2023-02-22 · 72% similar
SwissSign: Invalid stateOrProvinceName field
#1851164 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2023-09-01 · Closed 2023-09-22 · 72% similar
SwissSign: S/MIME wrong key Usage
#1908128 RESOLVED Self Reported Incident Certificate Misissuance Opened 2024-07-16 · Closed 2024-08-28 · 72% similar
NAVER Cloud Trust Services: Certificate issued with incorrect OCSP URI in AIA

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

Confirm action