Skip to content
Noroxi
NVD / CVE Program· CNA openssl

CVE-2024-12797: RFC7250 handshakes with unauthenticated servers don't abort as expected

Noroxi assessment

Priority: Monitor (action score 30/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.8% (FIRST EPSS); higher than 79.3% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: OpenSSL OpenSSL 3.2.4, 3.3.3, 3.4.1; azl3 cloud-hypervisor-cvm 38.0.72.2-3 on Azure Linux 3.0 38.0.72.2-3; azl3 cloud-hypervisor-cvm 41.0.79-3 on Azure Linux 3.0 38.0.72.2-3.

Low priority for now. Upgrade to OpenSSL OpenSSL 3.2.4, 3.3.3, 3.4.1; azl3 cloud-hypervisor-cvm 38.0.72.2-3 on Azure Linux 3.0 38.0.72.2-3; azl3 cloud-hypervisor-cvm 41.0.79-3 on Azure Linux 3.0 38.0.72.2-3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.4 · v3.1—No exploit Fix available
Published
Feb 11, 2025
Updated
Nov 6, 2026
EPSS
1.8% · 79th percentile

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
29 / 40 · 7.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 1.8%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-12797

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for openssl records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
opensslopenssl
netappsnapmanager
netappbrocade fabric operating system
netapph300s firmware
netapph300s
netapph500s firmware
netapph500s
netapph700s firmware
netapph700s
netapph410s firmware
netapph410s
netapph410c firmware

and 9 more

Check your server's TLS configuration

The OpenSSL version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.

Run the SSL check

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • netapp bootstrap osall versions
  • netapp brocade fabric operating systemall versions
  • netapp h300s firmwareall versions
  • netapp h410c firmwareall versions
  • netapp h410s firmwareall versions
  • netapp h500s firmwareall versions
  • netapp h610c firmwareall versions
  • netapp h610s firmwareall versions
  • netapp h615c firmwareall versions
  • netapp h700s firmwareall versions
  • netapp snapmanagerall versions
  • openssl openssl3.2.0 and later · before 3.2.4
  • openssl openssl3.4.0 and later · before 3.4.1
  • openssl openssl3.3.0 and later · before 3.3.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (openssl). Independent of NVD's CPE analysis and usually ahead of it.

  • OpenSSL OpenSSL

    • 3.4.0 and later · before 3.4.1affected · semver
    • 3.3.0 and later · before 3.3.3affected · semver
    • 3.2.0 and later · before 3.2.4affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9opensslbefore 1:3.2.2-6.el9_5.11:3.2.2-6.el9_5.1
AlmaLinux:9openssl-develbefore 1:3.2.2-6.el9_5.11:3.2.2-6.el9_5.1
AlmaLinux:9openssl-libsbefore 1:3.2.2-6.el9_5.11:3.2.2-6.el9_5.1
AlmaLinux:9openssl-perlbefore 1:3.2.2-6.el9_5.11:3.2.2-6.el9_5.1
Alpine:v3.20opensslfrom 3.2.0 · before 3.3.3-r03.3.3-r0
Debian:13opensslbefore 3.4.1-13.4.1-1
openSUSE:Tumbleweedopenssl-3before 3.2.4-1.13.2.4-1.1
PyPIcryptographyfrom 42.0.0 · before 44.0.144.0.1
Red Hat:enterprise_linux:10.0opensslbefore 1:3.2.2-16.el101:3.2.2-16.el10
Red Hat:enterprise_linux:10.0openssl-debuginfobefore 1:3.2.2-16.el101:3.2.2-16.el10
Red Hat:enterprise_linux:10.0openssl-debugsourcebefore 1:3.2.2-16.el101:3.2.2-16.el10
Red Hat:enterprise_linux:10.0openssl-develbefore 1:3.2.2-16.el101:3.2.2-16.el10
Red Hat:enterprise_linux:10.0openssl-libsbefore 1:3.2.2-16.el101:3.2.2-16.el10
Red Hat:enterprise_linux:10.0openssl-libs-debuginfobefore 1:3.2.2-16.el101:3.2.2-16.el10
Red Hat:enterprise_linux:10.0openssl-perlbefore 1:3.2.2-16.el101:3.2.2-16.el10
Red Hat:enterprise_linux:9::appstreamopenssl-debuginfobefore 1:3.2.2-6.el9_5.11:3.2.2-6.el9_5.1
Red Hat:enterprise_linux:9::appstreamopenssl-debugsourcebefore 1:3.2.2-6.el9_5.11:3.2.2-6.el9_5.1
Red Hat:enterprise_linux:9::appstreamopenssl-develbefore 1:3.2.2-6.el9_5.11:3.2.2-6.el9_5.1
Red Hat:enterprise_linux:9::appstreamopenssl-libs-debuginfobefore 1:3.2.2-6.el9_5.11:3.2.2-6.el9_5.1
Red Hat:enterprise_linux:9::appstreamopenssl-perlbefore 1:3.2.2-6.el9_5.11:3.2.2-6.el9_5.1
Red Hat:enterprise_linux:9::baseosopensslbefore 1:3.2.2-6.el9_5.11:3.2.2-6.el9_5.1
Red Hat:enterprise_linux:9::baseosopenssl-libsbefore 1:3.2.2-6.el9_5.11:3.2.2-6.el9_5.1
Rocky Linux:9opensslbefore 1:3.2.2-6.el9_5.11:3.2.2-6.el9_5.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7openssl-3before 3.2.3-150700.5.5.13.2.3-150700.5.5.1

Same product

openssl: all records

Other highest-scoring records for the same primary product.

  • CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remKEV
    90Now
  • CVE-2021-3711SM2 Decryption Buffer Overflow
    65This week
  • CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code
    65This week

Published before and after this one in the same product

  • ← EarlierCVE-2024-4741Nov 13, 2024 · Use After Free with SSL_free_buffers
    40Plan
  • ← EarlierCVE-2024-13176Jan 20, 2025 · Timing side-channel in ECDSA signature computation
    18Monitor
  • Later →CVE-2025-4575May 22, 2025 · The x509 application adds trusted use instead of rejected use
    26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
OpenSSL OpenSSL3.2.4Vendor (CNA)
OpenSSL OpenSSL3.3.3Vendor (CNA)
OpenSSL OpenSSL3.4.1Vendor (CNA)
azl3 cloud-hypervisor-cvm 38.0.72.2-3 on Azure Linux 3.038.0.72.2-3 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 cloud-hypervisor-cvm 41.0.79-3 on Azure Linux 3.038.0.72.2-3 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 openssl 3.3.2-2 on Azure Linux 3.03.3.3-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 openssl 3.3.3-1 on Azure Linux 3.03.3.3-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 cloud-hypervisor-cvm 38.0.72.2-5 on CBL Mariner 2.038.0.72.2-5 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 cloud-hypervisor-cvm 38.0.72.2-5 on CBL-Mariner 2.038.0.72.2-5 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:openssl1:3.2.2-6.el9_5.1 · AlmaLinux:9Package registry (OSV)
almalinux:openssl-devel1:3.2.2-6.el9_5.1 · AlmaLinux:9Package registry (OSV)
almalinux:openssl-libs1:3.2.2-6.el9_5.1 · AlmaLinux:9Package registry (OSV)
almalinux:openssl-perl1:3.2.2-6.el9_5.1 · AlmaLinux:9Package registry (OSV)
alpine:openssl3.3.3-r0 · Alpine:v3.20Package registry (OSV)
debian:openssl3.4.1-1 · Debian:13Package registry (OSV)
opensuse:openssl-33.2.4-1.1 · openSUSE:TumbleweedPackage registry (OSV)
PyPI:cryptography44.0.1Package registry (OSV)
red hat:openssl1:3.2.2-16.el10 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:openssl-debuginfo1:3.2.2-16.el10 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:openssl-debugsource1:3.2.2-16.el10 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:openssl-devel1:3.2.2-16.el10 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:openssl-libs1:3.2.2-16.el10 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:openssl-libs-debuginfo1:3.2.2-16.el10 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:openssl-perl1:3.2.2-16.el10 · Red Hat:enterprise_linux:10.0Package registry (OSV)
rocky linux:openssl1:3.2.2-6.el9_5.1 · Rocky Linux:9Package registry (OSV)
suse:openssl-33.2.3-150700.5.5.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
None

Weakness class (CWE)

CWE-392 · Missing Report of Error Condition

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. CVSS6.3 → 7.4
  2. Severitymedium → high
  3. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records