← Entrust cases
Bugzilla #1897630 Self Reported Incident

Entrust: Jurisdiction issue in some EV TLS & Code Signing certificates

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 identified a compliance issue involving 101 EV TLS certificates and 5 Code Signing EV certificates where the jurisdiction locality was incorrectly included, and the jurisdiction state or province field was missing. This was discovered during a routine scan with pkilint. Entrust confirmed the mis-issuance on May 16, 2024, and all affected certificates were revoked or expired by May 21, 2024. Entrust is preparing a full incident report and has implemented corrective measures to prevent future occurrences. They also filed reports for delayed reporting and revocation due to the timing of their internal processes.

Model: gpt-4o-mini Generated: 2026-06-13 21:39 UTC Revised: 2026-06-16 18:57 UTC Confidence: 0.85 28 comments
Chronology
  1. Entrust confirmed the mis-issuance of certificates.
  2. All affected certificates were revoked or expired.
Thread Activity
  1. Entrust representative — During a scan, we discovered 74 certificates with jurisdiction locality present and state/province missing.
  2. Entrust representative — All affected certificates had expired or were revoked by May 21, 2024.
  3. Entrust representative — We posted the full incident report detailing the findings and corrective actions.
  4. Entrust representative — We acknowledged the failure to notify relevant Root Programs about the incident.
  5. Entrust representative — All action items have been addressed, and we requested the incident be closed.
Participants
Entrust representative Community commenter Mozilla representative
External References
Related Bugzilla IDs Mentioned
Similar Local Cases
#1879602 RESOLVED Security Incident Self Reported Incident Opened 2024-02-09 · Closed 2024-07-19 · 100% similar
Entrust: OCSP response signed with SHA-1
#1894111 RESOLVED Ca Documents Self Reported Incident Opened 2024-04-29 · Closed 2025-01-22 · 100% similar
Entrust: Not updating CPR Problem Reporting Mechanism fields in CCADB
#1867130 RESOLVED Self Reported Incident Opened 2023-11-28 · Closed 2024-05-10 · 96% similar
Entrust: Jurisdiction Locality Wrong in EV Certificate
#1921387 RESOLVED Self Reported Incident Opened 2024-09-27 · Closed 2025-03-18 · 94% similar
Entrust: Improperly Verified Business Category
#1448986 RESOLVED Self Reported Incident Opened 2018-03-26 · Closed 2023-02-22 · 92% similar
Entrust: IP Address in dNSName form
#1914999 RESOLVED Self Reported Incident Opened 2024-08-26 · Closed 2025-02-28 · 91% similar
Entrust: S/MIME OrgID Country not matching C field
#1952635 RESOLVED Self Reported Incident Opened 2025-03-08 · Closed 2025-08-11 · 89% similar
Entrust: Missing or Inconsistent Disclosure of S/MIME BR Audits
#1658792 RESOLVED Self Reported Incident Opened 2020-08-12 · Closed 2023-02-22 · 88% similar
Entrust: Invalid data in State/Province Field

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

Confirm action