← eMudhra Technologies Limited cases
Bugzilla #1924492 Ccadb Metadata Update

eMudhra emSign PKI Services: Failure to Update CA Owner Information in CCADB

RESOLVED FIXED eMudhra Technologies Limited
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

The case reports that eMudhra emSign PKI Services had outdated contact information in the Common CA Database (CCADB). Mozilla’s thread states that on 7 October 2024 it was identified that the CCADB email intended for Certificate Problem Reporting was not kept up to date, even though the correct contact information was reflected in the CP/CPS. As a result, a certificate revocation request submitted on 31 August 2024 was delayed because it was sent to the general enquiry email address rather than the dedicated Certificate Problem Reporting channel. eMudhra initiated corrective action by updating the CCADB with the correct Problem Reporting contact details (with the CCADB update noted as completed on 10/09/2024 in the closure summary). The thread also describes remediation steps including introducing an internal procedure after a PA Committee meeting to review CCADB consistency when CP/CPS changes are made, and adding quarterly compliance audits to review both CP/CPS and CCADB entries. The bug is marked RESOLVED with resolution FIXED, and Mozilla indicated it would close the bug on 14-Feb-2025 unless issues or questions remained.

Model: gpt-5.4-nano Generated: 2026-06-13 21:26 UTC Revised: 2026-06-16 18:37 UTC Confidence: 0.86 5 comments
Chronology
  1. A certificate revocation request was submitted but was delayed because it was sent to the general enquiry email instead of the dedicated Certificate Problem Reporting contact.
  2. eMudhra raised an external Bugzilla incident to report the delay in revocation handling.
  3. Corrective action was initiated to update the CCADB with the correct Problem Reporting contact details.
  4. The CCADB was updated with the correct Problem Reporting contact details.
  5. An internal procedure was introduced to ensure CCADB entries are reviewed for consistency when CP/CPS changes are published, with independent second-level verification.
  6. Mozilla planned to close the bug unless there were issues or questions.
Thread Activity
  1. Emudhra representative — eMudhra reported that CCADB contact information for certificate problem reporting was outdated versus CP/CPS, causing revocation requests to be routed to the general enquiry channel and delaying handling.
  2. Emudhra representative — eMudhra requested the bug be closed if there were no further questions.
  3. Mozilla representative — Mozilla asked for a closure summary covering incident description, root cause(s), remediation, ongoing commitments, and an attestation that action items were completed.
  4. Emudhra representative — eMudhra provided an incident closure summary describing the CCADB update failure, root cause, remediation actions, and commitments including quarterly verification and training/resource measures.
  5. Mozilla representative — Mozilla stated it would close the bug on 14-Feb-2025 unless there were issues or questions.
Participants
Emudhra representative Mozilla representative
Related Bugzilla IDs Mentioned
Similar Local Cases
#2015567 RESOLVED Ccadb Metadata Update Incident Ccadb Disclosure Issue Information Request Opened 2026-02-09 · Closed 2026-05-15 · 68% similar
Government of Saudi Arabia, NIC (SDAIA): Missing Contact Information in CCADB
#1941853 RESOLVED Ccadb Metadata Update Opened 2025-01-15 · 67% similar
Entrust root has SECOM CPS in AllCertificateRecordsCSVFormatv2
#1818833 RESOLVED Ccadb Metadata Update Opened 2023-02-24 · Closed 2023-03-20 · 67% similar
IdenTrust: Inaccurate CRL Details in CCADB
#2007066 RESOLVED Ccadb Metadata Update Repository Issue Opened 2025-12-19 · Closed 2026-01-20 · 61% similar
Disig: Missing CA Disig R2I2 Certification Service Full CRL URLs in CCADB
#2012934 RESOLVED Ccadb Metadata Update Repository Issue Opened 2026-01-28 · Closed 2026-02-26 · 60% similar
Telia: Inccorrect CRL URL on a Root CA record in CCADB
#2031164 RESOLVED Ca Certificate Compliance Ccadb Metadata Update Incident Opened 2026-04-12 · Closed 2026-05-29 · 60% similar
Google Trust Services: Incomplete CRL Distribution Point URLs in CCADB for GTS Roots
#2049012 ASSIGNED Ccadb Metadata Update Incident Ccadb Disclosure Issue Policy Document Issue Opened 2026-06-19 Still Open · 59% similar
FNMT: Inaccuracy in CRL URL in CCADB
#1956681 RESOLVED Ccadb Metadata Update Policy Document Issue Opened 2025-03-27 · Closed 2025-05-08 · 59% similar
Entrust: Cross-certified CA CP/CPS not updated in CCADB

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

Confirm action