chore(security): a DoS and resource-limit review, its tests, and SECURITY.md for 0.1

Aperta
#61 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
15/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c
Ambito
security

Direzione di ricerca

This is a design-level review, not a single fix. Start by reading SECURITY.md and the QUIC, HPACK and QPACK code paths the issue names, and map each resource limit (streams, header and table sizes, reassembly buffers, ACK ranges, connection IDs) to where it is enforced. Done means a written internal review, a test per DoS class run against the server, DoS tests wired into CI, and a current SECURITY.md. Confirm scope with maintainers before starting.

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

Descrizione

P1: first release

SECURITY.md says the code hasn't had an external security review. That doesn't have to block 0.1, but a network stack shipping its own QUIC, HPACK and QPACK in C should do two things.

Before the tag:

  • An internal review pass over the attack surface. Resource limits per connection: streams, header and table sizes, reassembly buffers, CONTINUATION floods, QPACK blocked-stream memory, ACK range counts, and connection-ID tables. The known HTTP/2 and HTTP/3 DoS classes: rapid reset (CVE-2023-44487), CONTINUATION flood, HPACK bomb, ping and settings floods, zero-window stalls. Anti-amplification and Retry token handling.
  • Tests for each DoS class, run against our server.
  • The release notes and SECURITY.md say plainly what has and hasn't been reviewed, and how to report a vulnerability.

After 0.1: an external review, and an application to OSS-Fuzz once the targets from #55 exist.

Done when: the internal pass is written up, every finding is fixed or filed, the DoS tests are in CI, and SECURITY.md is current.

Lingua principale
C
Stelle
0
Fork
0
Merge medio
20h 4m
PR unite (30g)
25

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

Tutte le issue di public/cursed-http

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.