Use-after-free of caller-owned server name in client connection constructors

In rustls-ffi 0.12.0 through 0.15.6, rustlsclientconnectionnew and rustlsclientconnectionnewalpn retained a reference to the caller's servername buffer after returning, rather than copying it. The API documentation did not require the buffer to outlive the call and as a result if the caller freed...

rustls-ffi -- Read after free

The RusTLS project reports: functions retained a reference to the caller's servername buffer after returning, rather than copying it. The API documentation did not require the buffer to outlive the call and as a result if the caller freed or reused the buffer, later TLS processing read freed...

RusTLS FFI -- plaintext TLS handshake vulnerability

The RusTLS project reports: TLS 1.3 handshake message processing could allow a broken peer to send plaintext handshake messages where an encrypted one is expected without rustls rejecting the connection...

FreeBSD : RusTLS FFI -- plaintext TLS handshake vulnerability (ff969b25-b97b-11f1-b09d-8447094a420f)

The version of FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the ff969b25-b97b-11f1-b09d-8447094a420f advisory. The RusTLS project reports: TLS 1.3 handshake message processing could allow a broken peer to send...

GO-2025-3678 vulnerabilities

Vulnerabilities for packages: parseable, linkerd2-proxy, shadowsocks-rust, wasm-pack, linkerd-extension-init, lychee, qdrant, zola, cargo-audit, rustup, sdp-k8s-injector, rustls-ffi, uv, wash, wasmcloud, xh, zizmor, wasmtime, sqlx, rye, wadm, nushell, ntpd-rs, atuin, tealdeer, zed, kdash, oranda,...

GHSA-QG5G-GV98-5FFH rustls network-reachable panic in `Acceptor::accept`

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...

rustls network-reachable panic in `Acceptor::accept`

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...

RUSTSEC-2024-0399 rustls network-reachable panic in `Acceptor::accept`

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...

rustls network-reachable panic in `Acceptor::accept`

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...

PT-2024-40945 · Unknown +1 · Tokio-Rustls +2

Name of the Vulnerable Software and Affected Versions: rustls version 0.23.13 Description: A bug in rustls leads to a panic if the received TLS ClientHello is fragmented. This issue affects servers using rustls::server::Acceptor::accept and tokio-rustls's LazyConfigAcceptor API, but not those usi...

rustls-ffi (>=0.10.0, <=0.11.0) potentially affected by CVE-2024-32650 via rustls (>=0.21.0, <=0.21.5)

rustls CARGO version =0.21.0, =0.10.0, =0.11.0 Source cves: CVE-2024-32650 Source advisory: OSV:GHSA-6G7W-8WPP-FRHJ...

rustls-ffi (>=0.10.0, <=0.11.0) potentially affected by CVE-2024-32650 via rustls (>=0.21.0, <=0.21.5)

rustls CARGO version =0.21.0, =0.10.0, =0.11.0 Source cves: CVE-2024-32650 Source advisory: GHSA-6G7W-8WPP-FRHJ...

RUSTSEC-2024-0336 `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network input

If a closenotify alert is received during a handshake, completeio does not terminate. Callers which do not call completeio are not affected. rustls-tokio and rustls-ffi do not call completeio and are not affected. rustls::Stream and rustls::StreamOwned types use completeio and are affected...