rustsec-2024-0399
Vulnerability from osv_rustsec
Published
2024-11-22 12:00
Modified
2025-10-28 06:02
Summary
rustls network-reachable panic in `Acceptor::accept`
Details
A bug introduced in rustls 0.23.13 leads to a panic if the received
TLS ClientHello is fragmented. Only servers that use
rustls::server::Acceptor::accept() are affected.
Servers that use tokio-rustls's LazyConfigAcceptor API are affected.
Servers that use tokio-rustls's TlsAcceptor API are not affected.
Servers that use rustls-ffi's rustls_acceptor_accept API are affected.
{
"affected": [
{
"database_specific": {
"categories": [
"denial-of-service"
],
"cvss": null,
"informational": null
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "rustls",
"purl": "pkg:cargo/rustls"
},
"ranges": [
{
"events": [
{
"introduced": "0.23.0"
},
{
"fixed": "0.23.0"
},
{
"introduced": "0.23.13"
},
{
"fixed": "0.23.18"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"CVE-2024-11738",
"GHSA-qg5g-gv98-5ffh"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "A bug introduced in rustls 0.23.13 leads to a panic if the received\nTLS ClientHello is fragmented. Only servers that use\n`rustls::server::Acceptor::accept()` are affected.\n\nServers that use `tokio-rustls`\u0027s `LazyConfigAcceptor` API are affected.\n\nServers that use `tokio-rustls`\u0027s `TlsAcceptor` API are not affected.\n\nServers that use `rustls-ffi`\u0027s `rustls_acceptor_accept` API are affected.",
"id": "RUSTSEC-2024-0399",
"modified": "2025-10-28T06:02:18Z",
"published": "2024-11-22T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/rustls"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2024-0399.html"
},
{
"type": "REPORT",
"url": "https://github.com/rustls/rustls/issues/2227"
}
],
"related": [],
"severity": [],
"summary": "rustls network-reachable panic in `Acceptor::accept`"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…