← Entrust cases
Bugzilla #1802916 Ca Certificate Compliance Certificate Misissuance Remediation Tracking

Entrust: EV TLS certificates incorrectly indicated jurisdiction (misissuance)

RESOLVED FIXED Entrust
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

Entrust reported that it became aware of a problem with Verified Mark Certificates (VMCs) on 10 November 2022, and later determined the issue affected EV verification certificates that include jurisdiction information. Entrust investigated and found that 322 EV certificates were miss-issued with the incorrect jurisdiction. Entrust stated it did not stop issuance, but that the issues discovered through investigation were corrected. Entrust said it planned to revoke within the 5-day requirement; however, it reported delays due to subscriber pushback, coordination with technical teams, and an end-of-year black-out period, and it opened a late revocation incident report (Bug 1804753). Entrust also stated that 62 certificates were revoked during the planned 5-day revocation period, and that 14 certificates were incorrectly indicated as miss-issued and therefore would not be revoked. Entrust reported that a new jurisdiction functionality was deployed on 14 March 2023 and that it would use an approved incorporating agencies matrix for jurisdiction data alignment and post-issuance linting. Mozilla indicated it would close the bug on 19-Apr-2023, and the bug is marked RESOLVED with resolution FIXED.

Model: gpt-5.4-nano Generated: 2026-06-13 21:33 UTC Revised: 2026-06-16 18:54 UTC Confidence: 0.90 9 comments
Chronology
  1. Entrust became aware of a problem with VMC certificates.
  2. Entrust identified 322 EV certificates miss-issued with incorrect jurisdiction.
  3. Entrust reported revocation outcomes during the planned 5-day revocation period and identified 14 certificates that would not be revoked.
  4. Entrust posted an incident report for late revocation (Bug 1804753).
  5. Entrust deployed the new jurisdiction functionality.
  6. Mozilla planned to close the bug.
Thread Activity
  1. Entrust representative — Bruce Morton described Entrust’s awareness of the VMC problem, the investigation into EV verification certificates with jurisdiction data, and stated 322 EV certificates were found miss-issued with incorrect jurisdiction.
  2. Thisisntrocket representative — Matthias asked what a VMC is and questioned why it took until 2022-11-28 to discover the problematic EV certificates, and whether revocation was planned.
  3. Entrust representative — Bruce Morton explained that VMC means Verified Mark Certificate, discussed why jurisdiction data was difficult to search, and said Entrust planned to revoke within the 5-day requirement but expected delays due to the end-of-year black-out period.
  4. Entrust representative — Bruce Morton stated that 14 certificates were incorrectly indicated as miss-issued and would not be revoked.
  5. Entrust representative — Bruce Morton reported that 62 certificates were revoked during the planned 5-day revocation period and that a delayed revocation incident report would be opened to track completion.
  6. Entrust representative — Bruce Morton noted that the incident was posted for late revocation and linked to Bug 1804753.
  7. Entrust representative — Bruce Morton described the planned “new design” to align jurisdiction data using an approved incorporating agencies matrix and outlined a verification process, with a target update date of 31 March 2023.
  8. Entrust representative — Bruce Morton stated the jurisdiction functionality was deployed on 14 March 2023.
  9. Mozilla representative — Mozilla’s bwilson said they would close the bug on 19-Apr-2023 unless other concerns were raised.
Participants
Entrust representative Thisisntrocket representative Mozilla representative
Related Bugzilla IDs Mentioned
Similar Local Cases
#1906467 RESOLVED Ca Certificate Compliance Certificate Misissuance Closure Request Opened 2024-07-05 · Closed 2025-05-13 · 100% similar
Entrust: S/MIME mailbox address not in subjectAltName
#1906470 RESOLVED Ca Certificate Compliance Certificate Misissuance Closure Request Opened 2024-07-05 · Closed 2025-05-13 · 100% similar
Entrust: S/MIME mailbox address case mismatch between subject and subjectAltName
#1914065 RESOLVED Ca Certificate Compliance Certificate Misissuance Closure Request Opened 2024-08-20 · Closed 2025-02-28 · 100% similar
Entrust: S/MIME certificates lacking OU verification
#1744827 RESOLVED Certificate Misissuance Delayed Revocation Opened 2021-12-07 · Closed 2024-03-08 · 100% similar
Entrust: SSL Certificates issued with Un-verified IP Addresses
#1627346 RESOLVED Ca Certificate Compliance Self Reported Incident Certificate Misissuance Delayed Revocation Opened 2020-04-03 · Closed 2023-02-22 · 98% similar
Entrust: S/MIME Certificate Issued with Incorrect Policy OID
#1685370 RESOLVED Ca Certificate Compliance Certificate Misissuance Revocation Issue Opened 2021-01-06 · Closed 2023-02-22 · 98% similar
Entrust: Incorrect Business Category Value Discovered in an EV SSL Certificate
#1712106 RESOLVED Ca Certificate Compliance Certificate Misissuance Revocation Issue Opened 2021-05-20 · Closed 2023-02-22 · 97% similar
Entrust: Invalid localityName
#1887753 RESOLVED Certificate Misissuance Audit Finding Opened 2024-03-25 · Closed 2024-07-12 · 96% similar
Entrust: Delay in Updating CPS

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

Confirm action