← GlobalSign nv-sa cases
Bugzilla #1708834
Certificate Problem Report
GlobalSign: Invalid stateOrProvinceName and locality pair
RESOLVED
FIXED
GlobalSign nv-sa
AI Summary
GlobalSign issued certificates with incorrect state and locality values, specifically confusing 'Amsterdam' as a state instead of a locality. This issue was identified through multiple reports and led to a suspension of certificate issuance from the affected profile. GlobalSign has since acknowledged the error, revoked the problematic certificates, and implemented a validation rule to prevent similar misissuances in the future. The root causes included mistakes by validation specialists and misinterpretations of data sources.
Chronology
- Bug reported regarding invalid state and locality values.
- GlobalSign acknowledged the issue and suspended issuance.
- Root cause analysis completed.
- Validation rule implemented to prevent future misissuances.
- Changes to the sources database implemented.
Participants
George [:fozzie]
Arvid Vermote
Eva Vansteenberge
Ryan Sleevi
External References
Similar Local Cases
GlobalSign: Invalid stateOrProvinceName value
GlobalSign: Invalid countryName
GlobalSign: EV certificates with serialNumber Government Entity and businessCategory Private Organization
GlobalSign: Untimely revocation of TLS certificate after submission of private key compromise
GlobalSign: Incorrect OCSP Delegated Responder Certificate
GlobalSign: ICAs in CCADB, without EKU extension are listed in WTCA report but not in WTBR report
GlobalSign: Failure to revoke noncompliant ICA within 7 days
GlobalSign: Failure to revoke noncompliant ICA within 7 days