← iTrusChina Co., Ltd. cases
Bugzilla #2080679 Ca Certificate Compliance Incident Self Reported Incident Problem Reporting Failure

iTrusChina: OCSP response ECDSA signatureAlgorithm encoded with NULL parameters

ASSIGNED iTrusChina Co., Ltd.
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

iTrusChina reported that its OCSP responders for test websites returned ECDSA signatures with NULL parameters in the AlgorithmIdentifier, which it said violates BR Section 7.1.3.2.2 and RFC 5758. The issue was first identified on 2026-10-09 after a third-party Certificate Problem Report notified the CA. iTrusChina said the affected responders included "wtocsp-cdn.itrus.com.cn-ECC EV" and "wtocsp-cdn.itrus.com.cn-ECC OV," and that the same underlying OCSP response generation code affected its _vTrus ECC Root CA_ and three ICAs. The CA said it completed root cause analysis, prepared a remedial action plan, and updated the OCSP response generation program on 2026-10-19. The report states the incident involved no misissuances and that issuance was not stopped. The bug remains assigned, and the thread includes a full incident report with a timeline and related incident references.

Model: gpt-5.4-mini Generated: 2026-10-20 17:42 UTC Confidence: 0.96 3 comments
Chronology
  1. The OCSP response generation program with the encoding issue was first deployed.
  2. A third-party CPR notified iTrusChina that its test websites’ OCSP responses used ECDSA signatureAlgorithm with NULL parameters.
  3. iTrusChina updated the OCSP response generation program and said the issue was fixed.
Thread Activity
  1. iTrusChina Co., Ltd. — iTrusChina filed a preliminary incident report saying a CPR had reported OCSP responses with ECDSA signatureAlgorithm NULL parameters and that it would disclose a full report by 2026-10-23.
  2. iTrusChina Co., Ltd. — iTrusChina said root cause analysis was complete and remedial actions were underway, with the full incident report still being drafted.
  3. iTrusChina Co., Ltd. — iTrusChina submitted the full incident report, describing the affected responders, root cause, timeline, and remediation.
Participants
iTrusChina Co., Ltd.
Related Bugzilla IDs Mentioned
Similar Local Cases
#2077101 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Revocation Issue Opened 2026-10-01 Still Open · 74% similar
iTrusChina: Reusing CRLnumber and Missing NULL Parameter of CRL signatureAlgorithm
#2079641 ASSIGNED Ca Certificate Compliance Incident Externally Reported Incident Vulnerability Disclosure Opened 2026-10-08 Still Open · 72% similar
SwissSign: Incorrectly encoded OCSP extension
#2080796 ASSIGNED Ca Certificate Compliance Incident Externally Reported Incident Vulnerability Disclosure Opened 2026-10-12 Still Open · 69% similar
ACCV: OCSP responses include “archiveCutoff” in “responseExtensions”
#2060152 RESOLVED Ca Certificate Compliance Self Reported Incident Certificate Misissuance Policy Document Issue Opened 2026-08-03 · Closed 2026-09-28 · 68% similar
iTrusChina: Inconsistent EKUs in CP/CPS and Mis-issuance of TLS Certificates with clientAuth against CP/CPS
#1712664 RESOLVED Ca Certificate Compliance Opened 2021-05-25 · Closed 2023-02-22 · 59% similar
iTrusChina: verification errors for the roots' CRLs(ARL)
#611283 RESOLVED Ca Certificate Compliance Opened 2010-11-11 · Closed 2022-11-14 · 58% similar
StartCom cert not working in Firefox 4 beta
#2025248 RESOLVED Self Reported Incident Opened 2026-03-23 · Closed 2026-05-01 · 58% similar
iTrusChina: Failure to Provide Regular Incident Update
#1652581 RESOLVED Ca Certificate Compliance Opened 2020-07-13 · Closed 2023-02-22 · 58% similar
Google Trust Services: digitalSignature KeyUsage not set

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

⚠

Confirm action