Open Bug 2090925 Opened 7 days ago Updated 2 days ago

CFCA: Serial numbers do not contain at least 64 bits of CSPRNG output

Categories

(CA Program :: CA Certificate Compliance, task)

Tracking

(Not tracked)

ASSIGNED

People

(Reporter: songxinlei, Assigned: songxinlei)

Details

(Whiteboard: [ca-compliance])

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/157.0.0.0 Safari/537.36

Steps to reproduce

Preliminary Incident Report

Summary

  • Incident description: In comment 22 and comment 23 of Bug #2058918, a reporter noticed CFCA that the serial numbers of OV subscriber certificates show a fixed prefix, an apparently time-derived field, a marker and a tail consisting only of decimal characters, that are suspected insufficient CSPRNG output, and CFCA OV RSA OCA G2 and CFCA EV RSA OCA G2 are impacted. These related issues are being investigated, more details will be provided once the conclusion reached, and we're aware of the potential mass revocation required.
  • Relevant policies:
    • CA/Browser Forum Baseline Requirements v2.3.1, Section 7.1.2.7 (Subscriber (Server) Certificate Profile) — serialNumber MUST contain at least 64 bits of output from a CSPRNG.
  • Source of incident disclosure: Third-Party Report

Actual results

N/A

Expected results

N/A

Assignee: nobody → songxinlei
Type: defect → task
Whiteboard: [ca-compliance]
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true

Hi, here's a quick update:
this incident is directly caused by CA system upgrade introduced on different dates for the following ICAs:

  • CFCA EV OCA: introduced on 2025-12-11
  • CFCA OV OCA: introduced on 2025-02-05
  • CFCA TLS EV OCA: introduced on 2026-06-15
  • CFCA TLS OV OCA: introduced on 2025-06-15
  • CFCA EV RSA OCA G2: introduced on 2026-02-05
  • CFCA OV RSA OCA G2: introduced on 2026-02-05
  • CFCA EV ECC OCA G2: introduced on 2026-02-05
  • CFCA OV ECC OCA G2: introduced on 2026-02-05

The total number of certificates will be disclosed when confirmed, we're now conducting mass revocations for the valid certificates.
And, we plan to file another incident for delayed revocation within the next 24 hours, if the revocation process not going well.

Hi, we've filed a bug for the delay revocation, please track the process and details here: Bug #2092894

You need to log in before you can comment on or make changes to this bug.