CVE-2024-11738VulnerabilityPublished 6 Dec 2024Updated 20 Nov 2025

CVE-2024-11738: rustls · Uncaught Exception

Affects rustlsSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
crates.iogithub/rustls/rustls`pkg:cargo/github/rustls/rustls`Other threats	Affected =0.23.13	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade Rustls to a patched version once it becomes available from the maintainers to ensure the vulnerability is fully addressed. 2. In the interim, implement network-level filtering to detect and block anomalous fragmented TLS ClientHello messages that deviate from normal handshake patterns. 3. Employ rate limiting on TLS handshake requests to reduce the risk of DoS attacks exploiting this vulnerability. 4. Monitor application and system logs for frequent TLS handshake failures or unexpected crashes indicative of exploitation attempts. 5. Conduct thorough testing of TLS handshake handling in staging environments to identify and mitigate similar edge cases. 6. Consider deploying Web Application Firewalls (WAFs) or Intrusion Prevention Systems (IPS) with updated signatures capable of detecting malformed TLS handshake fragments. 7. Engage with Rustls community and security advisories for timely updates and patches. 8. For critical systems, implement redundancy and failover mechanisms to maintain service availability during potential attack attempts.

Description

A flaw was found in Rustls 0.23.13 and related APIs. This vulnerability allows denial of service (panic) via a fragmented TLS ClientHello message.

Impact

The primary impact of CVE-2024-11738 is denial of service, where an attacker can remotely crash applications using Rustls 0.23.13 by sending specially crafted fragmented TLS ClientHello messages. This can disrupt availability of critical services such as web servers, APIs, proxies, and embedded devices relying on Rustls for TLS termination. Although confidentiality and integrity remain intact, the loss of availability can lead to service outages, degraded user experience, and potential cascading failures in dependent systems. Organizations with internet-facing services using the vulnerable Rustls version are at risk of targeted DoS attacks, which could be leveraged as part of larger attack campaigns or to cause operational disruptions. The ease of exploitation (no authentication or user interaction required) increases the threat level. However, the absence of known exploits in the wild suggests limited current active exploitation. The scope includes any system or application embedding Rustls 0.23.13, which is popular in Rust-based software ecosystems. The medium severity rating reflects the moderate but significant risk posed by service interruptions.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 11:32 UTC

Technical details

References

Community reviews

Related threats