REDHAT-BUG-2517561: Medium severity OpenSSL OpenSSL vulnerability

Published Aug 17, 2026
·
Updated

A flaw was found in OpenSSL. OpenSSL CMP password based protection verification only checks whether the protectionAlg parameter was not NULL and not its ASN.1 type, before treating it as a PBMParameter. A crafted message can contain a parameter of a different type, which is then dereferenced as an invalid pointer.

A remote, unauthenticated attacker can crash an application acting as a CMP server that accepts PBM-protected messages, or a CMP client talking to a malicious or intercepted CMP server, resulting in a Denial of Service.

When verifying the password-based MAC protection of a CMP message, OpenSSL library reads the protectionAlg algorithm parameter with X509ALGORget0(), which returns both the parameter type and its value pointer. The value is then cast to an ASN1STRING and treated as the expected PBMParameter after only checking that pointer is not NULL. The parameter type returned by X509ALGORget0() was never consulted.

This happens during protection verification, before any MAC is computed, so no knowledge of the PBM shared secret is required; the only precondition is that PBM verification is reachable. On the server side this is reached from OSSLCMPSRVprocessrequest() for any application that stands up a CMP server accepting PBM-protected messages, and on the client side from CMP response validation against a malicious or on-path (MITM) server. The reliable consequence is a denial of service; there is no memory disclosure, no controlled memory write, and no path to code execution. CMP is a specialized feature that an application must explicitly enable.

As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.

OpenSSL 4.0, 3.6, 3.5, 3.4, 3.0 are vulnerable to this issue. OpenSSL 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.2. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.4. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.8. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.7. OpenSSL 3.0 users should upgrade to OpenSSL 3.0.22.

Affected Software

1 affected component
OpenSSL OpenSSL>=4.0.0<4.0.2, >=3.6.0<3.6.4, >=3.5.0<3.5.8, >=3.4.0<3.4.7, >=3.0.0<3.0.22

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade OpenSSL 3.0 to a version that resolves this vulnerability.

    Fixed in 3.0.22
  2. Upgrade

    Upgrade OpenSSL 3.4 to a version that resolves this vulnerability.

    Fixed in 3.4.7
  3. Upgrade

    Upgrade OpenSSL 3.5 to a version that resolves this vulnerability.

    Fixed in 3.5.8
  4. Upgrade

    Upgrade OpenSSL 3.6 to a version that resolves this vulnerability.

    Fixed in 3.6.4
  5. Upgrade

    Upgrade OpenSSL 4.0 to a version that resolves this vulnerability.

    Fixed in 4.0.2

Event History

Aug 17, 2026
Data Sourced
via Red Hat·07:34 PM
DescriptionSeverityAffected Software

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