← SwissSign AG cases
Bugzilla #1613334 Certificate Misissuance

SwissSign: Misissuance with misspellings in Location for a number of Certificates

RESOLVED FIXED SwissSign AG
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

SwissSign AG reported a misissuance incident involving 47 SSL and 113 S/MIME certificates that contained misspellings in the location fields. The issue was discovered during an audit on November 14, 2019, leading to the revocation of the affected certificates starting December 11, 2019. SwissSign implemented a manual process to prevent future misissuance and has since developed automated checks based on official standards. The incident report was filed on February 5, 2020, after the critical certificates were revoked. The CA acknowledged delays in reporting and revocation, which were attributed to the nature of the certificates' use in critical infrastructure. The case has been resolved with all identified certificates revoked.

Model: gpt-4o-mini Generated: 2026-06-13 20:50 UTC Revised: 2026-06-16 18:16 UTC Confidence: 0.85 22 comments
Chronology
  1. Discovery of misissued certificates during an audit.
  2. Acknowledgment of misissue and initiation of revocation.
  3. Incident report filed with Mozilla.
  4. Implementation of new automated checks.
  5. All affected certificates revoked.
Thread Activity
  1. SwissSign AG — Reported misissuance of certificates with misspellings.
  2. Mozilla representative — Questioned the delay in filing the incident report.
  3. Community commenter — Emphasized the need for timely reporting and revocation.
  4. SwissSign AG — Confirmed implementation of automated checks.
  5. SwissSign AG — Announced revocation of all affected certificates.
Participants
Community commenter
Related Bugzilla IDs Mentioned
Similar Local Cases
#1428877 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2018-01-08 · Closed 2023-02-22 · 90% similar
SwissSign: Invalid DNSName in SAN
#1506607 RESOLVED Self Reported Incident Certificate Misissuance Opened 2018-11-12 · Closed 2026-06-10 · 84% similar
SwissSign: Misissuance of Intermediate Certificates because of incorrect organizationIdentifier
#1894054 RESOLVED Certificate Misissuance Revocation Issue Opened 2024-04-29 · Closed 2024-07-03 · 84% similar
SwissSign: MPKI step-up process sets wrong JoI Locality
#1569651 RESOLVED Certificate Misissuance Opened 2019-07-29 · Closed 2023-02-22 · 83% similar
SwissSign: Misissuance of Leaf Certificates because of incorrect postcode
#1929189 RESOLVED Certificate Misissuance Policy Document Issue Opened 2024-11-05 · Closed 2025-07-01 · 82% similar
SwissSign: S/MIME certificates deviate from CPR
#2033000 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Policy Document Issue Opened 2026-04-17 · Closed 2026-07-09 · 82% similar
SwissSign: Certificate Profile error for S/MIME MV
#1636140 RESOLVED Certificate Misissuance Opened 2020-05-07 · Closed 2023-02-22 · 82% similar
SwissSign: duplicate serial number
#1731586 RESOLVED Ca Certificate Compliance Self Reported Incident Certificate Misissuance Opened 2021-09-20 · Closed 2023-02-22 · 82% similar
SwissSign: Certificate with key length 16258

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

Confirm action