Buypass: cRLNumber reused across Root CA CRLs
Categories
(CA Program :: CA Certificate Compliance, task)
Tracking
(Not tracked)
People
(Reporter: mads.henriksveen, Assigned: mads.henriksveen)
Details
(Whiteboard: [ca-compliance] [crl-failure])
Attachments
(1 file)
Preliminary Incident Report
Summary
-
Incident description:
A third party reported that CRLs for Buypass Class 2 Root CA and Buypass Class 3 Root CA reused the same cRLNumber accross two different versions of each Root CA CRLs.The report said that for each Root, the October CRL is a new CRL with a later thisUpdate and nextUpdate, but it carries the same cRLNumber as the June CRL. The revoked entries are the same in both.
-
Relevant policies:
- TLS Baseline Requirements v2.3.1, Section 7.2.2
- RFC 5280 Section 5.2.3
-
Source of incident disclosure:
Third Party Reported.
Updated•8 days ago
|
| Assignee | ||
Comment 1•1 day ago
|
||
Full Incident Report
Summary
- CA Owner CCADB unique ID: A000007
- Incident description: On 2026-06-02, after revoking the subordinate CAs Buypass Class 2 CA 5 and Buypass Class 3 CA 3, Buypass issued new CRLs for Buypass Class 2 Root CA and Buypass Class 3 Root CA in an extraordinary ceremony. These CRLs had CRL Number 34. In a scheduled root CRL ceremony on 2026-10-19, Buypass generated new CRLs for both roots with CRL Number 34 again, and published them on 2026-10-21. The October CRLs had a later thisUpdate and nextUpdate than the June CRLs, but the same revoked entries. A third party reported the issue on 2026-11-03. On 2026-11-04, Buypass published new CRLs for both roots with CRL Number 36.
- Timeline summary:
- Non-compliance start date: 2026-10-21 (publication of new CRLs reusing cRLNumber=34)
- Non-compliance identified date: 2026-11-03 (Certificate Problem Report received)
- Non-compliance end date: 2026-11-04 (publication of new CRLs with cRLNumber=36)
- Relevant policies:
- TLS Baseline Requirements v2.3.1, Section 7.2.2
- RFC 5280, Section 5.2.3
- Source of incident disclosure: Third Party Reported.
Impact
- Total number of certificates: Not applicable. The incident affected CRLs, not certificates.
- Total number of "remaining valid" certificates: Not applicable.
- Affected certificate types: Not applicable. Two CRLs were affected, one for each of Buypass Class 2 Root CA and Buypass Class 3 Root CA (see Appendix).
- Incident heuristic: The full set of affected CRLs is disclosed in the Appendix.
- Was issuance stopped? Not applicable. No certificates were affected.
- Analysis: The revoked entries in the June and October CRLs were identical, so no revocation information was lost or withheld. A relying party that uses the CRL Number to decide whether one CRL supersedes another could have treated the October CRL as not newer than the June CRL.
- Additional considerations: Buypass is discontinuing its TLS certificate services. See https://bugzilla.mozilla.org/show_bug.cgi?id=2085917.
Timeline
All times are UTC.
| Date and time (UTC) | Event |
|---|---|
| 2026-04-15 | Root CRLs with CRL Number 33 published for both roots. |
| 2026-06-02 | Buypass Class 2 CA 5 and Buypass Class 3 CA 3 revoked. New root CRLs with CRL Number 34 generated in an extraordinary ceremony and published, replacing the CRLs with CRL Number 33. |
| 2026-10-19 | Scheduled root CRL ceremony. New CRLs for both roots generated with CRL Number 34, which had already been used in June. |
| 2026-10-21 07:47 | New CRLs with CRL Number 34 published for both roots. Non-compliance starts. |
| 2026-11-03 18:53 | Certificate Problem Report received. An internal case was created automatically and on-call staff were alerted. |
| 2026-11-03 19:14 | Receipt of the report acknowledged to the reporter. |
| 2026-11-04 07:25 | Investigation started. Cause identified, and a decision made to issue new CRLs the same day. |
| 2026-11-04 12:29–12:40 | New CRLs with CRL Number 36 generated for both roots. |
| 2026-11-04 13:19 | New CRLs with CRL Number 36 published. Non-compliance ends. |
| 2026-11-04 13:42 | Preliminary incident report posted on Bugzilla. |
| 2026-11-04 13:56 | Reporter was informed that the CRLs had been replaced and that a bug had been filed. |
Related Incidents
These incidents involve the same requirement or similar CRL issuance failures.
| Bug | Date | Description |
|---|---|---|
| 1793642 | 2022-10 | GoDaddy: root CRLs lacked the CRL Number extension because of reused manual ceremony scripts. |
| 2075720 | 2026-09 | NETLOCK: a root CA CRL was served in two versions with the same cRLNumber (39), the second containing additional entries. |
| 2077101 | 2026-10 | iTrusChina: Reusing CRLnumber and Missing NULL Parameter of CRL signatureAlgorithm |
Root Cause Analysis
Contributing Factor #1: CRL Numbers set manually from templates in offline ceremonies
- Description: Root CRLs are generated in ceremonies on an offline CA. Staff prepare each ceremony from the templates used in the previous ceremony and update them with new CRL Numbers and dates. The extraordinary ceremony on 2026-06-02 used CRL Number 34. The templates for the scheduled ceremony on 2026-10-19 continued the CRL Number sequence from the previous scheduled ceremony and assigned CRL Number 34 again, without accounting for the number already used in June.
- Timeline: The template-based process has been in use since 2010. The error was introduced when the templates were prepared for the 2026-10-19 ceremony.
- Detection: Not detected internally. Reported by a third party on 2026-11-03.
- Interaction with other factors: The error reached a published CRL because no check compared the new CRL Number with the last issued one (Factor #2).
Contributing Factor #2: No verification of the CRL Number sequence before or at publication
- Description: The ceremony documentation was prepared and reviewed by different staff members, but the review did not compare the CRL Numbers with the last published CRL for each root. The CRL publication service does not check that a new CRL has a higher CRL Number than the CRL it replaces.
- Timeline: This process has been the same since 2010.
- Detection: Not detected internally.
- Interaction with other factors: Allowed the error from Factor #1 to be published.
Root Cause Analysis methodology used: 5 Whys.
Lessons Learned
- What went well: The Certificate Problem Report created an internal case and alerted on-call staff outside office hours. The cause was identified the next morning, and corrected CRLs were published about 18.5 hours after the report was received. The preliminary incident report was posted the same day.
- What didn't go well: CRL Numbers were assigned manually from templates, and an extraordinary ceremony was not taken into account in the next scheduled ceremony. Neither the ceremony review nor the publication service checked the CRL Number sequence. The process depends on a few people, and the issue was found by a third party rather than by Buypass.
- Where we got lucky: The June and October CRLs had identical revoked entries, so no revocation information was lost.
- Additional: None.
Action Items
| Action Item | Kind | Corresponding Root Cause(s) | Evaluation Criteria | Due Date | Status |
|---|---|---|---|---|---|
| Publish new CRLs with CRL Number 36 for Buypass Class 2 Root CA and Buypass Class 3 Root CA | Mitigate | #1 | CRLs with CRL Number 36 available at the disclosed URLs | 2026-11-04 | Complete |
| Add a check to the CRL publication service that rejects a CRL whose CRL Number is not higher than the currently published CRL for the same issuer | Prevent | #2 | A test CRL with a reused or lower CRL Number is rejected | 2026-12-08 | Ongoing |
| Update the root CRL ceremony procedure so that CRL Numbers are taken from the last issued CRL, including CRLs from extraordinary ceremonies, and add a checklist step to verify this | Prevent | #1, #2 | Procedure updated and used in the next ceremony | 2026-11-04 | Complete |
Appendix
The June and October CRLs share CRL Number 34 (0x22). The CRLs with CRL Number 36 replaced the October CRLs. The CRL files are attached to this bug.
| Issuer | CRL Number | Published | thisUpdate (UTC) | nextUpdate (UTC) |
|---|---|---|---|---|
| Buypass Class 2 Root CA | 34 (0x22) | 2026-06-02 | 2026-06-02 | 2026-11-01 |
| Buypass Class 2 Root CA | 34 (0x22), affected | 2026-10-21 | 2026-10-01 | 2027-05-01 |
| Buypass Class 2 Root CA | 36 (0x24), replacement | 2026-11-04 | 2026-11-04 | 2027-05-01 |
| Buypass Class 3 Root CA | 34 (0x22) | 2026-06-02 | 2026-06-02 | 2026-11-01 |
| Buypass Class 3 Root CA | 34 (0x22), affected | 2026-10-21 | 2026-10-01 | 2027-05-01 |
| Buypass Class 3 Root CA | 36 (0x24), replacement | 2026-11-04 | 2026-11-04 | 2027-05-01 |
| Assignee | ||
Comment 2•1 day ago
|
||
Description
•