vulns.co
/
GKData.io MCP and API Buy me a coffee

PortSwigger

Upstream HTTP framing and parser-consistency boundaries

This PortSwigger research explains how disagreement between proxies and origin servers about where requests end can break isolation on shared upstream connections. Using HTTP/2 for client connections does not remove the risk if an intermediary translates requests into HTTP/1.1.

Open the referenceResearch PaperReviewed 2026-10-03

How to use this reference

Review framing contracts across every intermediary, including protocol translation and connection reuse. Consider upstream HTTP/2, consistent validation and normalization, and isolation tradeoffs where legacy transport remains. Assess remediation against the architecture rather than relying on a front-end protocol label or filtering claim.

Before reading

  • HTTP request and response semantics
  • Reverse-proxy and origin-server architecture

Context and limits

  • Protocol migration is the researcher’s recommendation, not proof that every HTTP/2 implementation is secure.
  • Historical cases and vendor support observations do not establish current vulnerabilities or feature availability.
  • Linked operational material is omitted. No individual award qualification or testing authorization is implied.

Sources

  1. HTTP/1.1 must die: the desync endgamePortSwigger · reviewed 2026-10-03

Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software