Skip to content

Releases

0.23.46

Choose a tag to compare

@ctz ctz released this 14 Oct 09:51

Security-relevant fixes:

  • GHSA-h2v8-394m-p7vv: The built-in (but disabled by default) Brotli certificate decompression can allocate an attacker-controlled amount of memory up to 1 GiB before authentication *

  • GHSA-c8m5-c952-6cm4: Debug impls for Tls12ClientSessionValue and Tls13ClientSessionValue include secret data *

  • GHSA-w44r-93j7-qv28: An unauthenticated ServerHello poisons the per-name key-exchange hints, so later ClientHellos carry only a classical X25519 share. Thank you to @Adam010341 .

  • GHSA-vp88-798v-h67f: In rustls 0.23.44 and 0.23.45, application data that a client buffers before the handshake completes is sent to the server even when the server rejects Encrypted Client Hello (ECH). Thank you to @ramonmrc18.

Other fixes taken from main:

  • server: reject non-empty certificate_request_context in #3294 **
  • reject protected change_cipher_spec records in #3295 **
  • brotli: reject large-window streams in #3297 *
  • Avoiding printing secrets in session types in #3299 *
  • client: fail on ECH rejection before encrypting application data in #3300 *
  • server: only allow early data for first PSK in #3312 *
  • compress: reject trailing input in zlib and brotli decompressors in #3318 **
  • ech: hold the server to its hello retry request decision in #3325 **
  • conn: be more careful about confidentiality limits with 1.2 in #3332 *
  • Fixes related to I/O issues in #3333 *
  • Advance the HPKE sequence only after open succeeds in #3340 *
  • Timely 1.3 key updates in #3342 *

* Thanks to OpenAI [email protected] for submitting 13 findings to us, whose fixes are included in this release.
** Thanks to @Mounika2456 for their continued contribution of hardening and compliance fixes

What's Changed

  • [0.23] bogo: avoid flicker on error handling with an alert by @ctz in #3339
  • [0.23] Retain up to the requested LimitedCache capacity by @6d7770 in #3337
  • Prepare 0.23.46 by @djc in #3354
  • [0.23] Delay saving KX hint until handshake confirmation by @ctz in #3355

Full Changelog: v/0.23.45...v/0.23.46

0.23.45

Choose a tag to compare

@ctz ctz released this 14 Sep 15:10

Bug fix: TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries

Rustls accepted TLS 1.3 handshake messages sent at the wrong encryption level when they followed a key-changing message in the same record. The handshake transcript is still authenticated, so a network-position attacker cannot use this to alter or complete a handshake; the practical effect is that a peer could send handshake messages that should be encrypted in plaintext without rustls rejecting the connection.

This issue is tracked as GHSA-2mjx-qc3c-rqvc. This issue affects rustls versions 0.23.13 through 0.23.44 inclusive.

Note that this is functionally the same bug as GO-2026-4340.

What's Changed

Full Changelog: v/0.23.44...v/0.23.45

0.23.44

Choose a tag to compare

@djc djc released this 07 Sep 09:27
v/0.23.44

Support for post-quantum secure ML-DSA certificates is now enabled by default in the aws-lc-rs crypto provider. ML-DSA certificates are not supported in the public web PKI, but they can be used with private certificate hierarchies.

The built-in KeyLogFile implementation now creates files that are restricted to being read only by the owner.

What's Changed

  • [0.23] Enable ML-DSA by default by @djc in #3249
  • [0.23] Create SSLKEYLOGFILE with owner-only permissions by @djc in #3210
  • 0.23: verify server certificate against correct name on ECH rejection by @ctz in #3236
  • Fix internal rustls links in README.md to make it compatible with cra… by @Erik-Sovereign in #3239

0.23.43

Choose a tag to compare

@ctz ctz released this 29 Jul 16:13
  • Bug fix: corrected reachable panic in debug mode (or with overflow-checks) when decrypting a ticket of specific lengths with Rfc5077Ticketer (and therefore rustls::crypto::aws_lc_rs::Ticketer). This happens pre-authentication.

    This is not used in the default configuration, but using stateless resumption is common and this affects the aws-lc-rs provider. The ticketer associated with the ring provider is not affected.

  • Bug fix: A QUIC client using a CryptoProvider that mixes QUIC-capable and -incapable TLS1.3 suites can panic if the server chooses the QUIC-incapable suite.

  • Bug fix: A QUIC client would incorrectly accept a TLS1.2 server hello. A full handshake would require a trusted server that talks TLS1.2 in QUIC.

What's Changed

Full Changelog: v/0.23.42...v/0.23.43

0.23.42

Choose a tag to compare

@djc djc released this 13 Jul 15:27
v/0.23.42
  • Implemented support for "TLS Ticket Requests" (RFC 9149)
    • Client-side: a new optional ClientConfig.send_ticket_request configuration field was added to allow specifying TicketRequest parameters for requesting a specific number of TLS 1.3 session tickets from the server. Defaults to None, which skips sending the client extension and preserves current behavior.
    • Server-side: a new ServerConfig.max_tls13_tickets configuration field was added to allow setting an upper bound on the number of TLS 1.3 tickets sent in response to a client's request. Defaults to 0, which ignores the client's ticket requests extension and preserves current behavior.

What's Changed

  • Backport RFC 9149 ticket_request extension by @hz2 in #3132

0.23.41

Choose a tag to compare

@djc djc released this 22 Jun 13:30
v/0.23.41

What's Changed

  • Update read_buf API to match current nightly by @djc in #3102

0.23.40

Choose a tag to compare

@ctz ctz released this 28 Apr 15:58
  • ECH: correct implementation of RFC-recommended padding scheme for SNI names in the inner client hello.
  • ECH: correct padding of inner client hello when SNI is disabled.
  • Alter default of ServerConfig::require_ems based on provider's FIPS status. Prior to this change, the default followed the fips crate feature, which was less helpful for users of external FIPS-approved providers.

What's Changed

  • Default require_ems based on CryptoProvider FIPS status by @janrueth in #3034
  • 0.23.40: backport ECH padding fixes to 0.23 by @ctz in #3044

Full Changelog: v/0.23.39...v/0.23.40

0.23.39

Choose a tag to compare

@cpu cpu released this 22 Apr 21:30
v/0.23.39

Adapts to updated nightly for the non-default read_buf feature.

What's Changed

Full Changelog: v/0.23.38...v/0.23.39

0.23.38

Choose a tag to compare

@djc djc released this 12 Apr 21:27
v/0.23.38

What's Changed

  • Backport client: allow skipping selected ALPN validation by @TaeHagen in #3020

0.23.37

Choose a tag to compare

@cpu cpu released this 24 Feb 17:57
v/0.23.37

Adds support for ML-KEM-1024 key exchange.

What's Changed

Full Changelog: v/0.23.36...v/0.23.37