← Asseco Data Systems S.A. cases
Bugzilla #1567062 Self Reported Incident Audit Finding

Asseco DS / Certum: inconsistent disclosure of externally-operated intermediate

RESOLVED FIXED Asseco Data Systems S.A.
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

Asseco Data Systems S.A. (Certum) reported an inconsistency regarding the disclosure of an intermediate certificate that was cross-certified with SSL.com. The issue arose when it was found that the same Subject Public Key Info (SPKI) was associated with different Certificate Policy/Certification Practice Statements (CP/CPS) from both Certum and SSL.com. Following the report, Certum acknowledged the discrepancy and committed to reviewing their disclosures. They subsequently corrected the audit information for the affected certificates and confirmed that no further inconsistencies were found in their intermediate certificates. The case has been resolved with the necessary updates made.

Model: gpt-4o-mini Generated: 2026-06-13 18:18 UTC Revised: 2026-06-16 18:05 UTC Confidence: 0.85 13 comments
Chronology
  1. Asseco disclosed an inconsistency in the CP/CPS information for a cross-certified intermediate certificate.
  2. Asseco corrected the audit information for the affected certificates.
  3. Asseco confirmed no additional inconsistencies were found in their intermediate certificates.
Thread Activity
  1. Mm representative — Asseco has disclosed the following intermediate as being operated under the same CP/CPS as parent.
  2. Asseco Data Systems S.A. — Thank you for reporting this. We will inspect it and share our point of view soon.
  3. Asseco Data Systems S.A. — We fixed issues reported by crt.sh and set subject audit/CP/CPS information instead of issuer.
  4. Fastly representative — It appears that all questions have been answered and remediation is complete.
Participants
Community commenter
Similar Local Cases
#2044023 RESOLVED Certificate Misissuance Self Reported Incident Remediation Tracking Opened By Ca Opened 2026-06-01 · Closed 2026-07-02 · 82% similar
Asseco DS / Certum: Cross-Certificates subject encoding discrepancy
#1409766 RESOLVED Ca Certificate Compliance Self Reported Incident Certificate Misissuance Opened 2017-10-18 · Closed 2023-02-22 · 81% similar
Asseco DS / Certum: CAA Mis-Issuance on CNAME pointing directly to restrictive CAA record
#1815355 RESOLVED Ca Certificate Compliance Self Reported Incident Opened 2023-02-07 · Closed 2023-08-16 · 81% similar
Asseco DS / Certum: Cross-Signed non-EV-audited root with an EV-enabled root
#1611458 RESOLVED Self Reported Incident Opened 2020-01-24 · Closed 2023-02-22 · 80% similar
Asseco DS / Certum: Invalid value in SAN dNSName
#1639502 RESOLVED Self Reported Incident Opened 2020-05-20 · Closed 2023-02-22 · 80% similar
Asseco DS / Certum: Incorrect OCSP response encoding
#1667684 RESOLVED Self Reported Incident Opened 2020-09-27 · Closed 2023-02-22 · 80% similar
Asseco DS / Certum: Failure to provide a preliminary report within 24 hours.
#1711208 RESOLVED Self Reported Incident Certificate Misissuance Opened 2021-05-14 · Closed 2023-02-22 · 80% similar
Asseco DS / Certum: Incorrect localityName
#1832093 RESOLVED Self Reported Incident Certificate Misissuance Opened 2023-05-09 · Closed 2023-06-02 · 80% similar
Asseco DS / Certum: Subordinate certificates with sequential serial number

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

Confirm action