REDHAT-BUG-2430388: Null Pointer Dereference

Published Jan 16, 2026
·
Updated

Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1TYPE 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 TSRESPverifyresponse() 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 osslessgetsigningcert() and osslessgetsigningcertv2() access the signing cert attribute value without validating its type. When the type is not VASN1SEQUENCE, this results in accessing invalid memory through the ASN1TYPE 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.

OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.

OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.

OpenSSL 3.4 users should upgrade to OpenSSL 3.4.4.

OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.

OpenSSL 3.0 users should upgrade to OpenSSL 3.0.19.

OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1ze. (premium support customers only).

Affected Software

1 affected component
OpenSSL OpenSSL>=1.1.1<=1.1.1, >=3.0<=3.6, >=3.5<=3.5, >=3.4<=3.4, >=3.3<=3.3, >=3.6<=3.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade OpenSSL 1.1.1 to a version that resolves this vulnerability.

    Fixed in 1.1.1ze
  2. Upgrade

    Upgrade OpenSSL 3.0 to a version that resolves this vulnerability.

    Fixed in 3.0.19
  3. Upgrade

    Upgrade OpenSSL 3.3 to a version that resolves this vulnerability.

    Fixed in 3.3.6
  4. Upgrade

    Upgrade OpenSSL 3.4 to a version that resolves this vulnerability.

    Fixed in 3.4.4
  5. Upgrade

    Upgrade OpenSSL 3.5 to a version that resolves this vulnerability.

    Fixed in 3.5.5
  6. Upgrade

    Upgrade OpenSSL 3.6 to a version that resolves this vulnerability.

    Fixed in 3.6.1

Event History

Jan 16, 2026
Data Sourced
via Red Hat·02:42 PM
DescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of REDHAT-BUG-2430388?

The severity of REDHAT-BUG-2430388 is classified as moderate, indicating a potential for disruption in vulnerable systems.

2

How do I fix REDHAT-BUG-2430388?

To fix REDHAT-BUG-2430388, update the OpenSSL package to a patched version as recommended in the security advisories.

3

What types of systems are affected by REDHAT-BUG-2430388?

Systems running specific versions of OpenSSL, including 1.1.1 and versions from 3.0 to 3.6, are affected by REDHAT-BUG-2430388.

4

What kind of attack does REDHAT-BUG-2430388 expose systems to?

REDHAT-BUG-2430388 may lead to denial of service through a pointer dereference when processing malformed TimeStamp Response files.

5

Is there a workaround for REDHAT-BUG-2430388?

Currently, there are no known workarounds for REDHAT-BUG-2430388; updating OpenSSL is the recommended solution.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203