test(fuzz): libFuzzer targets for the QUIC, HTTP/2, HTTP/3, HPACK and QPACK decoders

Abierto
#55 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c, github-actions

Línea de trabajo

Start with the existing HTTP/1 targets in fuzz/fuzz_fastparse.c and fuzz/fuzz_chunked.c, and the make fuzz target, to see how a libFuzzer target is built and run under ASan and UBSan. Then read the entry points in hpack.h, qpack.h, h2.h, h3.h and quic.h to choose one decoder for a first target. Done means that target runs in CI, with its seed corpus and any crashes saved under fuzz/regressions/. The whole-connection targets and the remaining decoders are larger follow-up work.

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

Descripción

enhancement P0: release blocker

libFuzzer only covers the HTTP/1 parsers today (fuzz/fuzz_fastparse.c, fuzz_fbparse.c, fuzz_batchparse.c, fuzz_chunked.c). Nothing fuzzes the other decoders of untrusted network input, and those are where memory-safety bugs in a C network stack would be:

  • quic.h: packet header and frame decoding, transport parameters, ACK ranges, stream reassembly
  • hpack.h and qpack.h: header block decoding, the dynamic tables, and QPACK encoder/decoder stream instructions
  • h2.h and h3.h: frame parsing and the stream state machines

Plan:

  1. One libFuzzer target per decoder, with seed corpora taken from the existing tests' traffic (nghttp2, nghttp3 and ngtcp2 runs).
  2. A whole-connection target: an established quic_conn (keys from a fixed handshake) fed fuzzed decrypted payloads, so the frame handlers are reached past packet protection. The same for h2_recv and h3_recv.
  3. Run them in CI with the HTTP/1 targets (make fuzz), and add their crashes to fuzz/regressions/.

Done when: every decoder above has a target running in CI under ASan and UBSan, and a long local run (hours per target) finds nothing open.

Lenguaje dominante
C
Estrellas
0
Forks
0
Merge medio
20 h 4 min
PR fusionados (30 d)
25

Preparar el entorno

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 public/cursed-http

Todos los issues de public/cursed-http

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.