ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2024-12797

Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don't abort as exp

Published Feb 11, 2025 · catalog updated Nov 7, 2026 · Issue summary: Clients using

Last checked Nov 7, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2024-12797. EPSS is 1.86%. Act only if a listed version of Issue summary: Clients using is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Issue summary: Clients using).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
High7.4
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
1.86%
Remediation
Version ranges on file
Affected products
Alpine:v3.20 openssl · Alpine:v3.21 openssl · Alpine:v3.22 openssl · Alpine:v3.23 openssl · Alpine:v3.24 openssl · cpe netapp/brocade fabric operating system

Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don't abort as expected when the SSL_VERIFY_PEER verification mode is set. Impact summary: TLS and DTLS connections using raw public keys may be vulnerable to man-in-middle attacks when server authentication failure is not detected by clients. RPKs are disabled by default in both TLS clients and TLS servers. The issue only arises when TLS clients explicitly enable RPK use by the server, and the server, likewise, enables sending of an RPK instead of an X.509 certificate chain. The affected clients are those that then rely on the handshake to fail when the server's RPK fails to match one of the expected public keys, by setting the verification mode to SSL_VERIFY_PEER. Clients that enable server-side raw public keys can still find out that raw public key verification failed by calling SSL_get_verify_result(), and those that do, and take appropriate action, are not affected. This issue was introduced in the initial implementation of RPK support in OpenSSL 3.2. The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Alpine:v3.20 openssl3.2.0 → 3.3.3-r0
  • Alpine:v3.21 openssl3.2.0 → 3.3.3-r0
  • Alpine:v3.22 openssl3.2.0 → 3.3.3-r0
  • Alpine:v3.23 openssl3.2.0 → 3.3.3-r0
  • Alpine:v3.24 openssl3.2.0 → 3.3.3-r0
  • cpe netapp/brocade fabric operating systemversion unspecified
  • cpe netapp/h300s firmwareversion unspecified
  • cpe netapp/h500s firmwareversion unspecified
  • cpe netapp/h700s firmwareversion unspecified
  • cpe netapp/snapmanagerversion unspecified
  • cpe openssl/openssl< 3.2.4
  • cpe openssl/openssl< 3.3.3
  • cpe openssl/openssl< 3.4.1

How to fix CVE-2024-12797

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2024-12797. EPSS is 1.86%. Act only if a listed version of Issue summary: Clients using is installed.

Which versions are affected?

Compare what you have installed with 3.2.0 → 3.3.3-r0, < 3.2.4, < 3.3.3, < 3.4.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-392. EPSS 1.86%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

OpenSSL security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Feb 11, 2025 · NIST NVD

    Detected

    Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don't abort as expected when the SSL_VERIFY_PEER verification mode is set. Impact summary: TLS and DTLS connections using raw public keys may be vulnerable to man-in-middle attacks when server authentication failure is not detected by cli

  2. Nov 6, 2026 · NIST NVD

    Updated

    Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don't abort as expected when the SSL_VERIFY_PEER verification mode is set. Impact summary: TLS and DTLS connections using raw public keys may be vulnerable to man-in-middle attacks when server authentication failure is not detected by cli

  3. Nov 6, 2026 · NIST NVD

    Updated

    Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don't abort as expected when the SSL_VERIFY_PEER verification mode is set. Impact summary: TLS and DTLS connections using raw public keys may be vulnerable to man-in-middle attacks when server authentication failure is not detected by cli

  4. Nov 7, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    openssl fixed in 3.3.3-r0; openssl fixed in 3.3.3-r0; openssl fixed in 3.3.3-r0; openssl fixed in 3.3.3-r0

  5. Nov 7, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    openssl fixed in 3.3.3-r0

  6. Nov 7, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don't abort as expected when the SSL_VERIFY_PEER verification mode is set. Impact summary: TLS and DTLS connections using raw public keys may be vulnerable to man-in-middle attacks when server authentication failure is not detected by cli

Sources

  • CVE.orgVulnerability recordCVE-2024-12797

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2024-12797

    30-day exploitation probability 1.86%

    first.org
  • NIST NVDVulnerability recordCVE-2024-12797

    Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don't abort as expected when the SSL_VERIFY_PEER verification mode is set. Impact summary: TLS and DTLS connections u

    nvd.nist.gov
  • OpenSSF OSV / OSV ScannerPackage advisoryALPINE-CVE-2024-12797
    osv.dev
  • Trivy Vulnerability DBPackage advisoryALPINE-CVE-2024-12797

    Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don't abort as expected when the SSL_VERIFY_PEER verification mode is set. Impact summary: TLS and DTLS connections us

    osv.dev

References

Freshness

Last verified in this catalog Nov 7, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Trivy Vulnerability DBNov 7, 2026
  • OpenSSF OSV / OSV ScannerNov 7, 2026
  • FIRST EPSSNov 7, 2026
  • CVE.orgNov 7, 2026
  • NIST NVDNov 7, 2026