Access of Resource Using Incompatible Type ('Type Confusion') Affecting openssl-debuginfo package, versions <1:3.2.2-1.amzn2023.0.5


Severity

Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.08% (23rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Access of Resource Using Incompatible Type ('Type Confusion') vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-AMZN2023-OPENSSLDEBUGINFO-15320910
  • published19 Feb 2026
  • disclosed27 Jan 2026

Introduced: 27 Jan 2026

CVE-2025-69420  (opens in a new tab)
CWE-843  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 openssl-debuginfo to version 1:3.2.2-1.amzn2023.0.5 or higher.
This issue was patched in ALAS2023-2026-1434.

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl-debuginfo package and not the openssl-debuginfo package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file.

Impact summary: An application calling TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.

The functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2() access the signing cert attribute value without validating its type. When the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.

Exploiting this vulnerability requires an attacker to provide a malformed TimeStamp Response to an application that verifies timestamp responses. The TimeStamp protocol (RFC 3161) is not widely used and the impact of the exploit is just a Denial of Service. For these reasons the issue was assessed as Low severity.

The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the TimeStamp Response implementation is outside the OpenSSL FIPS module boundary.

OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.

OpenSSL 1.0.2 is not affected by this issue.

CVSS Base Scores

version 3.1