← GlobalSign nv-sa cases
Bugzilla #1535873 Certificate Misissuance

GlobalSign: AT&T Insufficient Serial Number Entropy

RESOLVED FIXED GlobalSign nv-sa
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

GlobalSign discovered a compliance issue related to insufficient serial number entropy in certificates issued by AT&T, a customer using an on-premise CA. Upon notification, AT&T was instructed to halt issuance and update their configurations. They successfully upgraded their EJBCA version to support 128-bit serial numbers and began reissuing certificates. By April 16, 2019, all misissued certificates with 63-bit serial numbers had been revoked. GlobalSign is in the process of closing down all subordinate CAs operated by third parties, with a target completion date of August 2019 for most, while ensuring future compliance.

Model: gpt-4o-mini Generated: 2026-06-13 18:08 UTC Revised: 2026-06-16 18:44 UTC Confidence: 0.90 16 comments
Chronology
  1. GlobalSign notified AT&T of the serial number issue and instructed them to stop issuance.
  2. All misissued certificates with 63-bit serial numbers were revoked.
  3. GlobalSign confirmed plans to close down all subordinate CAs hosted by third parties.
Thread Activity
  1. Fastly representative — Doug Beattie posted an incident report detailing the compliance issue with AT&T's certificates.
  2. Community commenter — AT&T provided a status update on their upgrade to support 128-bit serial numbers.
  3. Community commenter — AT&T reported revocation of over 42,000 certificates as part of their remediation efforts.
  4. Fastly representative — Confirmation received that GlobalSign is finalizing the closure of subordinate CAs.
Participants
Fastly representative Community commenter
External References
Similar Local Cases
#1547691 RESOLVED Certificate Misissuance Opened 2019-04-29 · Closed 2023-02-22 · 96% similar
GlobalSign: AT&T SSL certificates without the AIA extension
#1552586 RESOLVED Self Reported Incident Certificate Misissuance Opened 2019-05-17 · Closed 2023-02-22 · 95% similar
GlobalSign: 4 Misissued certificates with invalid CN
#1524877 RESOLVED Certificate Misissuance Opened 2019-02-03 · Closed 2023-02-22 · 94% similar
GlobalSign: IP in dnsName
#1599775 RESOLVED Self Reported Incident Certificate Misissuance Opened 2019-11-27 · Closed 2023-02-22 · 85% similar
GlobalSign: Wrong business category (Non Commercial Entity when should have been Private Organization)
#1708834 RESOLVED Certificate Misissuance Self Reported Incident Opened 2021-04-30 · Closed 2023-02-22 · 78% similar
GlobalSign: Invalid stateOrProvinceName and locality pair
#1866806 RESOLVED Self Reported Incident Certificate Misissuance Opened 2023-11-27 · Closed 2024-02-01 · 78% similar
GlobalSign: S/MIME Sponsor validated certificates with CommonName value equal to OrganizationName
#1707073 RESOLVED Certificate Misissuance Self Reported Incident Opened 2021-04-22 · Closed 2023-02-22 · 77% similar
GlobalSign: Invalid countryName
#1934790 RESOLVED Certificate Misissuance Self Reported Incident Opened 2024-12-03 · Closed 2025-01-14 · 77% similar
GlobalSign: OV TLS certificate with incorrect countryName value for organization

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

Confirm action