RUSTSEC-2026-0523: MAX_STREAM_DATA frame can open streams beyond the stream limit

Abierto
  • ¿Algo no está bien?
#38 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
security

Línea de trabajo

The payload names only the vulnerable crate, quinn-proto 0.11.17, and the patched range >=0.11.19; it does not show where the gateway uses it. Start with cargo tree -i quinn-proto to see whether it is a direct or transitive dependency, then check Cargo.toml and Cargo.lock. Done when the lockfile resolves to a patched version, cargo build and the test suite pass, and cargo audit no longer reports RUSTSEC-2026-0523.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

MAX_STREAM_DATA frame can open streams beyond the stream limit

Details
Package quinn-proto
Version 0.11.17
URL https://github.com/quinn-rs/quinn/commit/3eb7465d9e11d7a245e99cde1a4eb872ec26d264
Date 2026-09-30
Patched versions >=0.11.19
Unaffected versions <0.11.0

When a MAX_STREAM_DATA frame named a peer-initiated bidirectional stream that was not open yet, received_max_stream_data treated the stream, and every lower-numbered stream, as opened without checking the stream ID against the limit advertised to the peer. RFC 9000 section 4.6 requires closing the connection with STREAM_LIMIT_ERROR in this case, and the STREAM and RESET_STREAM handlers already did so.

After the handshake, a peer can send one small MAX_STREAM_DATA frame naming a very large stream index, and accept then yields every stream up to that index. In quinn, a loop that keeps calling accept_bi can be handed more than 2^40 streams. Depending on the runtime, the endpoint runs out of memory, stops accepting new connections, or keeps busy indefinitely, even after the peer has gone away. Clients and servers that accept peer-initiated bidirectional streams are affected. Unidirectional streams are not.

The fix validates the stream ID in received_max_stream_data and adds a defensive check where streams are opened implicitly. It is in 0.11.19.

See advisory page for additional details.

Lenguaje dominante
Rust
Estrellas
0
Forks
2
Merge medio
14 d 2 h
PR fusionados (30 d)
1

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de stackabletech/postgresql-trino-gateway

Todos los issues de stackabletech/postgresql-trino-gateway

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.