← Autoridad de Certificacion Firmaprofesional cases
Bugzilla #1464335 Ca Certificate Compliance

Firmaprofesional: Undisclosed intermediate certificate SIGNE

RESOLVED FIXED Autoridad de Certificacion Firmaprofesional
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

Firmaprofesional reported that after issuing a technically constrained sha256withRSA SIGNE subordinate CA (an intermediate certificate), it did not disclose the certificate into the CCADB as required. The CA stated it became aware of the issue through a Mozilla Bugzilla process and referenced a related Bugzilla bug (1455119). In response, Firmaprofesional said it disclosed the affected certificate and updated its internal hierarchy procedures to add CCADB disclosure as a step when issuing new CA certificates. The thread also notes that CCADB was being updated to properly detect intermediate certificates requiring disclosure based on current disclosure requirements for email certificates. A component suggestion was raised by another participant, but the CA’s described remediation focused on disclosure and procedure updates. The bug is marked RESOLVED with resolution FIXED.

Model: gpt-5.4-nano Generated: 2026-06-13 17:49 UTC Revised: 2026-06-16 18:05 UTC Confidence: 0.86 4 comments
Chronology
  1. Firmaprofesional issued a technically constrained sha256withRSA SIGNE subordinate CA and later identified that it had not been disclosed into CCADB.
  2. Firmaprofesional opened the CA Program bug reporting the undisclosed intermediate certificate and requesting disclosure.
  3. CCADB updates were noted to improve detection of intermediate certificates requiring disclosure.
  4. The bug was resolved as FIXED.
Thread Activity
  1. Isigma representative — Reported that after issuing the technically constrained sha256withRSA SIGNE subordinate CA, Firmaprofesional did not disclose it into CCADB and said it should have.
  2. Isigma representative — Provided details including that internal procedures did not include CCADB disclosure for new CA certificates, and stated the CA disclosed the affected certificate and modified internal hierarchy procedures to add the disclosure step.
  3. Softvision representative — Suggested changing the component to NSS::CA Certificate Mis-Issuance if that was the correct component.
  4. Fastly representative — Stated that CCADB was being updated to properly detect intermediate certificates requiring disclosure based on current disclosure requirements for email certificates.
Participants
Isigma representative Fastly representative Softvision representative
Related Bugzilla IDs Mentioned
Similar Local Cases
#1538638 RESOLVED Ca Certificate Compliance Self Reported Incident Revocation Issue Opened 2019-03-25 · Closed 2023-02-22 · 97% similar
Firmaprofesional: AC Firmaprofesional - INFRAESTRUCTURA insufficient serial number entropy
#1398240 RESOLVED Ca Certificate Compliance Incident Opened 2017-09-08 · Closed 2023-02-22 · 94% similar
Firmaprofesional: Non-BR-Compliant OCSP Responders
#1368171 RESOLVED Ca Certificate Compliance Incident Opened 2017-05-26 · Closed 2024-06-30 · 89% similar
Firmaprofesional: Non-audited, non-technically-constrained intermediate certificates
#1649943 RESOLVED Ca Certificate Compliance Opened 2020-07-02 · Closed 2023-02-22 · 87% similar
Firmaprofesional: Incorrect OCSP Delegated Responder Certificate
#1700145 RESOLVED Ca Certificate Compliance Opened 2021-03-22 · Closed 2023-02-22 · 86% similar
Firmaprofesional: incorrect reserved CA/B Forum OIDs in certificates
#1771722 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2022-05-30 · Closed 2023-02-22 · 80% similar
Firmaprofesional: 2022 - Title field
#1717795 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Opened 2021-06-23 · Closed 2023-02-22 · 79% similar
Firmaprofesional: 2021 Audit Report Finding 3 out of 3
#1769240 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2022-05-13 · Closed 2023-02-22 · 79% similar
Firmaprofesional: 2022 - SSL certificates issued with wrong Organization ID number

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

Confirm action