← Chunghwa Telecom cases
Bugzilla #2025231 Delayed Revocation

Chunghwa Telecom: Test Website certificate not revoked

RESOLVED FIXED Chunghwa Telecom
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

Chunghwa Telecom (CHT) received a notification from a third party on 2026-03-22 that its test website (https://revoked.epkiov.hinet.net/) was serving a certificate recorded in CCADB as valid rather than revoked, which CHT stated was non-compliant with TLS Baseline Requirements Section 2.2 publication of information. CHT’s incident report says the non-compliance began on 2026-03-12 and ended on 2026-03-22. In the reported timeline, a scheduled automated script issued and revoked some test certificates, but a manual certbot renew command was executed for the FQDN while the revocation procedure (certbot revoke) was inadvertently omitted. After receiving the third-party report, CHT’s PKI Incident Response Team revoked the affected certificate on 2026-03-22. The report also states that CHT conducted a comprehensive review of all test certificates and enhanced the test certificate automation workflow and implemented a test certificate status monitoring mechanism. CHT requested closure, and the CCADB incident reporting process indicated a final call for comments before closing around 2026-04-24.

Model: gpt-5.4-nano Generated: 2026-06-13 21:38 UTC Revised: 2026-06-16 18:11 UTC Confidence: 0.86 8 comments
Chronology
  1. A scheduled automated process issued and attempted to revoke test certificates, but a later manual issuance for revoked.epkiov.hinet.net omitted the revocation step.
  2. A third party reported that the test website was serving a valid certificate instead of the required revoked certificate; CHT then revoked the affected certificate.
  3. CHT submitted a final incident report describing root cause, remediation, and requesting closure.
Thread Activity
  1. Cht representative — Filed a preliminary incident report stating a third party reported that the test website-revoked certificate was shown as valid in CCADB, causing non-compliance with BR Section 2.2.
  2. Cht representative — Posted the full incident report with timeline, impact (1 certificate), root cause (revocation omitted during manual step and lack of automated monitoring), and remediation (immediate revocation and workflow/monitoring improvements).
  3. Cht representative — Stated that CHT was continuing to monitor the issue.
  4. Cht representative — Stated that CHT was continuing to monitor the issue.
  5. Cht representative — Provided additional incident report text including remediation details and requested closure after stating all action items were completed.
  6. CCADB representative — Issued a final call for comments and indicated the incident would be closed approximately 2026-04-24.
Participants
Cht representative CCADB representative
Related Bugzilla IDs Mentioned
Similar Local Cases
#2009043 RESOLVED Delayed Revocation Opened 2026-01-07 · Closed 2026-02-19 · 100% similar
Chunghwa Telecom: Delayed disclosure to Bug 2008782 GTLSCA Audit Incident Report #1 - mass certificate revocation plan
#1903066 RESOLVED Delayed Revocation Opened 2024-06-17 · Closed 2025-02-12 · 86% similar
Chunghwa Telecom: Delayed Revocation with Controversial Extension (2.5.29.9, SubjectDirectoryAttributes)
#1899466 RESOLVED Delayed Revocation Opened 2024-05-29 · Closed 2024-09-13 · 80% similar
Chunghwa Telecom: Controversial Values within Extension (2.5.29.9, subjectDirectoryAttributes)
#1892419 RESOLVED Delayed Revocation Opened 2024-04-19 · Closed 2025-02-12 · 79% similar
Chunghwa Telecom: Delayed Revocation Due to GTLSCA EKU Misissuance
#1959278 RESOLVED Delayed Revocation Opened 2025-04-08 · Closed 2025-06-24 · 79% similar
Chunghwa Telecom: Delayed revocation for bug 1951415
#1951415 RESOLVED Certificate Misissuance Delayed Revocation Opened 2025-03-03 · Closed 2025-05-08 · 76% similar
Chunghwa Telecom: Failure to check restrictive CAA record during Migration
#2014833 RESOLVED Delayed Revocation Opened 2026-02-05 · Closed 2026-03-02 · 71% similar
FNMT: Delayed response to CPR sender related bug 2012326
#2016066 RESOLVED Delayed Revocation Opened 2026-02-11 · Closed 2026-03-30 · 70% similar
Firmaprofesional: Delayed preliminary response under BR 4.9.5 (Bug #2009941)

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

Confirm action