← NAVER Cloud Trust Services cases
Bugzilla #1772411 Self Reported Incident

NAVER Cloud Trust Services: Failure to Respond to May 2022 Survey

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

Mozilla cited the Root Store Policy requirement that CA operators must respond to Mozilla surveys with accurate information within the defined timescale. The May 31, 2022 deadline for NAVER Cloud Trust Services’ May 2022 Communication and Survey response was missed. Mozilla stated that no certificates were involved in the incident. NAVER Cloud reported that it received an email on May 17, 2022 indicating the response due date, received reminders on June 1 and June 3, and then submitted responses to the June 3 survey. NAVER Cloud attributed the missed deadline to negligence and said it would comply with the response deadline in the future. NAVER Cloud also described remediation steps, including sharing the survey content internally immediately, registering a task in its scheduling tool, and monitoring via daily alarms before deadlines. The bug was resolved as FIXED, and Mozilla indicated it would close the case on or about June 10, 2022.

Model: gpt-5.4-nano Generated: 2026-06-13 20:55 UTC Revised: 2026-06-16 18:31 UTC Confidence: 0.86 5 comments
Chronology
  1. NAVER Cloud Trust Services missed the May 31, 2022 deadline to respond to the May 2022 Communication and Survey.
  2. NAVER Cloud Trust Services submitted survey responses after receiving reminders and a Bugzilla notification.
  3. Mozilla planned to close the case on or about June 10, 2022.
Thread Activity
  1. Community commenter — Mozilla opened the case, stating NAVER Cloud failed to respond by May 31, 2022 as required by Root Store Policy section 4.2.
  2. Navercorp representative — NAVER Cloud stated it submitted responses to the June 3 survey.
  3. Community commenter — Mozilla requested an incident report and pointed to related incident-report guidance and other bugs.
  4. Navercorp representative — NAVER Cloud described how it became aware of the problem, provided a timeline of emails and notifications, stated no certificates were involved, explained the cause as negligence, and listed remediation steps with monitoring via daily alarms.
  5. Community commenter — Mozilla said it would close the bug on or about Friday, 10-June-2022.
Participants
Community commenter Navercorp representative
Related Bugzilla IDs Mentioned
Similar Local Cases
#1908128 RESOLVED Self Reported Incident Certificate Misissuance Opened 2024-07-16 · Closed 2024-08-28 · 89% similar
NAVER Cloud Trust Services: Certificate issued with incorrect OCSP URI in AIA
#1908130 RESOLVED Self Reported Incident Certificate Misissuance Opened 2024-07-16 · Closed 2024-08-28 · 88% similar
NAVER Cloud Trust Services: Incorrect keyUsage for ECC certificate
#1843268 RESOLVED Self Reported Incident Opened 2023-07-13 · Closed 2024-05-09 · 78% similar
NAVER Cloud Trust Services: OV certificate issued with OU field
#1914383 RESOLVED Incident Certificate Misissuance Self Reported Incident Opened 2024-08-22 · Closed 2024-12-11 · 67% similar
Telekom Security: CRL-Entries with wrong CRL Reason Codes
#1827490 RESOLVED Self Reported Incident Opened 2023-04-11 · Closed 2023-06-02 · 67% similar
Cybertrust Japan: CRL signature algorithm encoding error
#1649961 RESOLVED Self Reported Incident Opened 2020-07-02 · Closed 2023-02-22 · 67% similar
Actalis: Incorrect OCSP Delegated Responder Certificate
#1649962 RESOLVED Self Reported Incident Opened 2020-07-02 · Closed 2023-02-22 · 66% similar
SECOM: Incorrect OCSP Delegated Responder Certificate
#1671410 RESOLVED Self Reported Incident Opened 2020-10-15 · Closed 2024-06-30 · 66% similar
IdenTrust: Inconsistent Disclosure of Externally-Operated Intermediate

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

Confirm action