Skip to content

fix: reject framing on CONNECT requests - #53

Open
mcollina wants to merge 1 commit into
ShogunPanda:mainfrom
mcollina:security/sec-12-connect-framing
Open

mcollina wants to merge 1 commit into
ShogunPanda:mainfrom
mcollina:security/sec-12-connect-framing

Conversation

@mcollina

Copy link
Copy Markdown
Contributor

Reject request-body framing on CONNECT before switching to tunnel mode.

Milo previously entered the tunnel as soon as it recognized CONNECT, so bytes declared as a request body by Content-Length or Transfer-Encoding were instead exposed as tunnel data. Intermediaries that honored the framing could disagree about the message boundary.

CONNECT requests now reject either framing header, including Content-Length: 0. Unframed CONNECT requests retain their existing tunnel behavior, and the request-only guard preserves externally marked CONNECT response handling.

Rust, mirrored WASM, and fuzz conformance regressions cover both framing forms and the positive unframed tunnel path. The full Rust/fuzz and 100-test WASM suites pass, including focused non-SIMD validation.

This fixes SEC-12 from #38.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant