Hello,
I found a reproducible memory-safety issue in ls-qpack's QPACK decoder.
A small crafted decoder input can trigger a heap-use-after-free in the decoder path. I confirmed this on a clean checkout of the current repository using a standalone file-input reproducer with AddressSanitizer.
I would prefer not to disclose the PoC input or full technical details publicly before the maintainers have had a chance to review them.
I have prepared a small report package containing:
- affected commit information
- minimized PoC input
- standalone reproducer
- AddressSanitizer log
- plain-build result
- callback lifetime check
- root cause notes
- suggested fix direction
Is there an appropriate private contact or preferred security reporting channel for this issue?
Best regards,
Yukimura
Hello,
I found a reproducible memory-safety issue in ls-qpack's QPACK decoder.
A small crafted decoder input can trigger a heap-use-after-free in the decoder path. I confirmed this on a clean checkout of the current repository using a standalone file-input reproducer with AddressSanitizer.
I would prefer not to disclose the PoC input or full technical details publicly before the maintainers have had a chance to review them.
I have prepared a small report package containing:
Is there an appropriate private contact or preferred security reporting channel for this issue?
Best regards,
Yukimura