test(fuzz): libFuzzer targets for the QUIC, HTTP/2, HTTP/3, HPACK and QPACK decoders
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c, github-actions
- Domain
- networking, testing-qa
Research direction
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.
Written by the indexing model from the issue text.
Description
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 reassemblyhpack.handqpack.h: header block decoding, the dynamic tables, and QPACK encoder/decoder stream instructionsh2.handh3.h: frame parsing and the stream state machines
Plan:
- One libFuzzer target per decoder, with seed corpora taken from the existing tests' traffic (nghttp2, nghttp3 and ngtcp2 runs).
- 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 forh2_recvandh3_recv. - Run them in CI with the HTTP/1 targets (
make fuzz), and add their crashes tofuzz/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.
- Dominant language
- C
- Stars
- 0
- Forks
- 0
- Avg merge
- 20h 4m
- Merged PRs (30d)
- 25
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from public/cursed-http
-
P0: release blocker
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
public/cursed-http#56 ·
Maintainers usually reply within 1 day
-
P1: first release
Difficulty 5/5 Over a week Newbie friendliness 15/100
public/cursed-http#61 ·
Maintainers usually reply within 1 day
-
P0: release blocker
Difficulty 4/5 3-5 days Newbie friendliness 35/100
public/cursed-http#60 ·
Maintainers usually reply within 1 day
-
documentation P0: release blocker
Difficulty 3/5 1-2 days Newbie friendliness 42/100
public/cursed-http#59 ·
Maintainers usually reply within 1 day
-
P0: release blocker
Difficulty 4/5 3-5 days Newbie friendliness 35/100
public/cursed-http#58 ·
Maintainers usually reply within 1 day
All issues in public/cursed-http
Similar issues
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
xerial/sqlite-jdbc#1515 ·
Maintainers usually reply within 1 day
-
macOS 菜单栏托盘图标保留橙色,与系统单色图标风格不一致Possibly taken @xhugoliu claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
YizhengWw/HachimoDock#56 · 1 comment ·
-
compiler-rt:asan
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
llvm/llvm-project#242921 ·
Maintainers usually reply within 1 day
-
Missing gcc __builtin_stdc_bit_width/floor/ceil signature makes intellisense wrongly report error 70Open
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
microsoft/vscode-cpptools#14874 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FujiNetWIFI/fujinet-firmware#2401 ·
Maintainers usually reply within 1 day