← SwissSign AG cases
Bugzilla #1798316 Certificate Problem Report

SwissSign: 'c/o' in streetAddress of EV certificate

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 reported that, during an internal review of EV certificates on 31 October 2022, it detected eight EV certificates (four “pre” and four “certs”) containing a forbidden “c/o” entry in the “streetAddress” field. The CA stated that its vetting process falsely accepted the invalid values and that its checklists did not clearly forbid “c/o”. SwissSign said it started the mis-issued certificate process, searched for similar false verification on customer-managed PKIs, updated its verification checklists, and changed the configuration of the involved customers. The thread includes CT search links for the affected certificates and notes that the certificates were revoked by the customer on 28 September 2022, with the remaining EV certificate revoked as of 2022-11-04 15:44:33 UTC. SwissSign also reported implementing a technical safeguard to check customer certificate configuration for specific words such as “c/o” and “Postfach” and to forbid their use in EV certificate issuance. Mozilla indicated it would close the bug on or about 2 December 2022 unless additional questions or concerns were raised, and the bug is marked RESOLVED with resolution FIXED.

Model: gpt-5.4-nano Generated: 2026-06-13 20:49 UTC Revised: 2026-06-16 18:19 UTC Confidence: 0.50 3 comments
Chronology
  1. SwissSign detected eight EV certificates with a forbidden 'c/o' value in the streetAddress field during an internal review.
  2. SwissSign revoked the remaining EV certificate (as of 2022-11-04 15:44:33 UTC) and implemented a technical safeguard.
  3. Mozilla planned to close the bug unless additional questions or concerns were raised.
Thread Activity
  1. SwissSign AG — Mike Guenther described how SwissSign discovered the issue during an internal EV certificate review, provided a timeline of actions (including starting the mis-issued certificate process and updating checklists), and listed CT links for the affected certificates.
  2. SwissSign AG — Mike Guenther reported that the remaining EV certificate was revoked as of 2022-11-04 15:44:33 UTC and that a technical safeguard was implemented to forbid words such as 'c/o' and 'Postfach' in EV issuance.
  3. Mozilla representative — Ben Wilson stated Mozilla would close the bug on or about 2-Dec-2022 unless additional questions or concerns were raised.
Participants
SwissSign AG Mozilla representative
Similar Local Cases
#1670894 RESOLVED Certificate Misissuance Opened 2020-10-13 · Closed 2023-02-22 · 46% similar
SwissSign: Invalid stateOrProvinceName field
#1734131 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2021-10-05 · Closed 2023-02-22 · 46% similar
SwissSign: wrong address in EV certificate
#1766255 RESOLVED Certificate Misissuance Self Reported Incident Opened 2022-04-25 · Closed 2023-02-22 · 43% similar
SwissSign: Mis-Issuance of S/MIME certificates
#1691704 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2021-02-09 · Closed 2023-02-22 · 42% similar
SwissSign: Certificate with key length 4098 bit
#1784881 RESOLVED Policy Document Issue Self Reported Incident Opened 2022-08-15 · Closed 2023-02-22 · 42% similar
SwissSign: Missed deadline of publication of 6 CPs and 1 CP/CPS
#1849364 RESOLVED Revocation Issue Self Reported Incident Opened 2023-08-18 · Closed 2023-09-22 · 42% similar
SwissSign: Missed revocation and opening Bugzilla
#1851164 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2023-09-01 · Closed 2023-09-22 · 42% similar
SwissSign: S/MIME wrong key Usage
#1662137 RESOLVED Delayed Revocation Opened 2020-08-31 · Closed 2023-02-22 · 41% similar
SwissSign: OCSP responder unreachable

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

Confirm action