Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

RUSTSEC-2026-0347: Buffered application data sent to outer server after ECH rejection

Ouverte
  • Quelque chose ne va pas ?
#21 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
2/5
Temps estimé
1-3 heures
Accessibilité débutants
55/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
rust
Domaine
networking, security

Piste de recherche

The fix is a dependency bump: the rustls version in Cargo.toml and Cargo.lock must resolve to 0.23.46 or later. Start with the rustls entries in Cargo.toml and Cargo.lock, then run cargo update -p rustls and cargo test. Done when the lockfile pins a patched rustls and the build and tests pass. Check the advisory page for any API changes that affect ECH handling in this crate.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Buffered application data sent to outer server after ECH rejection

Details
Package rustls
Version 0.23.45
URL https://github.com/rustls/rustls/pull/3300
Date 2026-10-14
Patched versions >=0.23.46
Unaffected versions <0.23.44

When a server rejects Encrypted Client Hello (ECH), the client completes the
handshake using the outer ClientHello and authenticates the server against the
ECH config's public_name. At the end of that handshake, rustls encrypted and
queued any application data buffered via ClientConnection::writer() before
queueing the ech_required alert.

The application correctly receives
Error::PeerIncompatible(ServerRejectedEncryptedClientHello), but the next
write_tls() call (needed to send the alert) also sends the buffered
application data. Plaintext meant for the inner server therefore goes to the
client-facing server named by public_name.

That server is authenticated, so this is not exploitable by an unauthenticated
party, but it violates RFC 9849 section 6.1.6, which requires the client to
abort with ech_required "before sending any application data to the server".

This affects only clients that:

  • use EchMode::Enable (GREASE ECH is not affected),
  • write application data before the handshake completes, and
  • connect to a server that rejects their ECH config (for example, because it is stale).

The underlying ordering bug is older, but before 0.23.44 the client checked
the server certificate against the inner server name rather than public_name,
so certificate verification failed first and no data was sent.

See advisory page for additional details.

Langage dominant
Rust
Étoiles
1
Forks
0
Merge moyen
1 j 15 h
PR mergées (30 j)
3

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de stackabletech/stackable-odbc-trino

Toutes les issues de stackabletech/stackable-odbc-trino

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.