← SwissSign AG cases
Bugzilla #1876771 Certificate Misissuance Revocation Issue

SwissSign: RAO field modifications not saved, causing mis-issuance of OV 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 reported that during a review of its new web shop integration, it discovered that during the RAO check, modifications to regulated fields (Organization and State) were not saved into issued certificates. SwissSign stated this led to mis-issued certificates with wrong contents, affecting 11 precerts and 11 OV TLS certificates issued since 22 December 2023. After confirming the mis-issuance, SwissSign stopped RAO approval for certificates ordered via the web shop during the internal investigation and then resumed issuance once correct issuance was ensured. SwissSign identified a bug in the OV RAO approval process and mitigated it by exchanging the OV RAO process with the EV process, resulting in a fully compliant RAO process. SwissSign later updated the case to state that all affected certificates were revoked and that no further action was planned if there were no further community questions. Mozilla indicated it would keep the bug open for discussion until 7 February 2024.

Model: gpt-5.4-nano Generated: 2026-06-13 20:49 UTC Revised: 2026-06-16 18:21 UTC Confidence: 0.90 3 comments
Chronology
  1. SwissSign began issuing OV TLS certificates affected by the RAO field-saving problem in the new web shop integration.
  2. SwissSign received an internal report during review of the new web shop integration that field modifications were not saved into certificates during the RAO check.
  3. SwissSign reported that all affected certificates had been revoked and updated the bug timeline.
Thread Activity
  1. SwissSign AG — Created the incident report stating that RAO-modified Organization and State fields were not saved into certificates, resulting in mis-issuance of 11 precerts and 11 OV TLS certificates, and described mitigation by switching the OV RAO process to the EV process.
  2. SwissSign AG — Updated the case to say all certificates were revoked, corrected a timeline typo, and stated no further action was planned if there were no further community questions.
  3. Mozilla representative — Said the bug would remain open for another week until 7 February 2024 in case of further discussion.
Participants
SwissSign AG Mozilla representative
External References
Similar Local Cases
#1874196 RESOLVED Certificate Misissuance Revocation Issue Opened 2024-01-11 · Closed 2024-03-27 · 99% similar
SwissSign: difference in upper and lower case between CN field and SAN
#1734131 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2021-10-05 · Closed 2023-02-22 · 91% similar
SwissSign: wrong address in EV certificate
#1670894 RESOLVED Certificate Misissuance Opened 2020-10-13 · Closed 2023-02-22 · 90% similar
SwissSign: Invalid stateOrProvinceName field
#1851164 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2023-09-01 · Closed 2023-09-22 · 90% similar
SwissSign: S/MIME wrong key Usage
#1691704 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2021-02-09 · Closed 2023-02-22 · 89% similar
SwissSign: Certificate with key length 4098 bit
#1825232 RESOLVED Certificate Misissuance Self Reported Incident Opened 2023-03-29 · Closed 2023-03-31 · 89% similar
SwissSign: Invalid CT data in issued certs (SABRE.CT misconfiguration)
#1866091 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2023-11-22 · Closed 2023-12-11 · 89% similar
SwissSign: EV JurisdictionStateOrProvinceName - one certificate not selected for revocation
#1677737 RESOLVED Ca Certificate Compliance Certificate Misissuance Opened 2020-11-17 · Closed 2023-02-22 · 87% similar
SwissSign: duplicate serial number

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

Confirm action