Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

RUSTSEC-2026-0339: Unbounded growth of pending connection ID retirements in quinn-proto

Aperta
  • Qualcosa non va?
#15 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
20/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
networking, security

Direzione di ricerca

The report describes an already corrected vulnerability in quinn-proto 0.11.17, with the affected path in NEW_CONNECTION_ID processing. Read the linked advisory and pull request for the fix details, then check whether this repository uses an affected quinn-proto version; done means confirming the dependency is patched or identifying a specific remaining update.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Unbounded growth of pending connection ID retirements in quinn-proto

Details
Package quinn-proto
Version 0.11.16
URL https://github.com/quinn-rs/quinn/pull/2790
Date 2026-08-17
Patched versions >=0.11.17
Unaffected versions <0.6.0

When processing a NEW_CONNECTION_ID frame, quinn-proto queues a RETIRE_CONNECTION_ID frame for
each connection ID that the peer asked it to retire. The normal path bounds this queue and closes
the connection with a CONNECTION_ID_LIMIT_ERROR if the bound would be exceeded. However, the path
handling a connection ID that had already been retired pushed onto the queue without applying
the limit and without deduplicating.

A peer that has completed the handshake can first send a NEW_CONNECTION_ID frame with a large
retire_prior_to value to advance the receiver's connection ID window, and then repeatedly send
NEW_CONNECTION_ID frames with sequence numbers below that window. Each such frame adds another
entry to the queue. The queue is only drained by sending RETIRE_CONNECTION_ID frames, which are
subject to congestion control, so a peer that withholds acknowledgements can stall the drain while
continuing to flood, growing the victim's memory use without bound.

The flaw was corrected in 0.11.17 by applying the same limit on the already-retired path.

Thanks to @scadastrangelove for reporting this issue.

See advisory page for additional details.

Lingua principale
Rust
Stelle
1
Fork
0
Merge medio
1g 15h
PR unite (30g)
3

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di stackabletech/stackable-odbc-trino

Tutte le issue di stackabletech/stackable-odbc-trino

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.