caelum0x a6c662f100 fix(engine): cap request Content-Length to prevent unbounded body buffering
The native Rust HTTP server trusted the client-supplied Content-Length
header with no upper bound, looping to read the full claimed body size
with no cap. A tiny request claiming a huge Content-Length let a single
unauthenticated connection force unbounded memory allocation (DoS).

Reject any Content-Length over the existing 1MB request-size guard
before entering the body-accumulation loop.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-11-07 02:59:32 +03:00
..