Security readout for executives and security teams
Plain-English summary
A malformed timestamp response can crash software that asks OpenSSL to verify timestamp responses. The effect is denial of service, not data theft or code execution. OpenSSL says the timestamp protocol is not widely used and assessed the issue as Low severity, although the supplied CVSS score is 7.5 for availability impact.
Executive priority
Treat as targeted availability risk, not an emergency broad compromise. Patch during normal vulnerability windows unless a critical service processes untrusted timestamp responses, in which case prioritize sooner because a crash could interrupt business operations.
Technical view
In TS_RESP_verify_response(), ossl_ess_get_signing_cert() and _v2() access an ASN1_TYPE union member without confirming V_ASN1_SEQUENCE. A malformed RFC 3161 TimeStamp Response can trigger invalid or NULL pointer dereference. Affected branches listed are OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, and 1.1.1; 1.0.2 is not affected.
Likely exposure
Exposure is limited to applications that accept and verify TimeStamp Response files using OpenSSL TS_RESP_verify_response(). General OpenSSL use does not prove exposure. The OpenSSL FIPS modules in 3.5, 3.4, 3.3, and 3.0 are stated as not affected because this code is outside the FIPS boundary.
Exploitation context
The source bundle does not show active exploitation, and KEV is false. Exploitation requires delivering a malformed timestamp response to an application that verifies it. The documented impact is application crash and denial of service only.
Researcher notes
The key uncertainty is practical reachability. Confirm whether applications expose RFC 3161 timestamp verification to untrusted input. Patch references are provided for 3.6.1, 3.5.5, 3.4.4, 3.3.6, and 3.0.19. The bundle does not include an OpenSSL 1.1.1 patch reference.
Mitigation direction
- Upgrade affected OpenSSL branches using vendor-supported fixed releases or patch guidance.
- Prioritize systems that ingest untrusted RFC 3161 timestamp responses.
- Check downstream vendor advisories for embedded OpenSSL exposure and update packages.
- For OpenSSL 1.1.1, confirm support status and vendor remediation path.
- Avoid processing untrusted timestamp responses where the feature is not required.
Validation and detection
- Inventory OpenSSL versions across servers, appliances, containers, and applications.
- Identify code paths calling TS_RESP_verify_response() or timestamp response verification features.
- Confirm whether timestamp responses can be supplied by untrusted users or partners.
- Verify deployed OpenSSL includes the relevant branch patch or vendor package fix.
- Track Siemens or other product advisories for affected third-party products.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-754: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-69420 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- OpenSSL AdvisoryCVE reference, openssl · vendor-advisory
- 3.6.1 git commitCVE reference, openssl · patch
- 3.5.5 git commitCVE reference, openssl · patch
- 3.4.4 git commitCVE reference, openssl · patch
- 3.3.6 git commitCVE reference, openssl · patch
- 3.0.19 git commitCVE reference, openssl · patch
- https://cert-portal.siemens.com/productcert/html/ssa-265688.htmlCVE reference, siemens-SADP
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Check for Unusual or Exceptional Conditions
Improper Check for Unusual or Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.