Course contentsShow
← Security
Lesson 1112 of 3,05223. Web Security - Modern Web AttacksFree lesson

HTTP/2 Downgrade and Smuggling

Exploiting HTTP/2 to HTTP/1.1 translation inconsistencies to enable new smuggling attack vectors.

HTTP/2 Downgrade and Smuggling

You'll learn how attackers exploit the translation process between HTTP/2 and HTTP/1.1 to create smuggling opportunities that didn't exist in either protocol alone.

The Translation Problem

Modern web infrastructure often uses HTTP/2 between clients and reverse proxies, but HTTP/1.1 for backend communication. When your reverse proxy (like a CDN or load balancer) translates HTTP/2 requests into HTTP/1.1, subtle inconsistencies can emerge—and attackers can weaponize them.

Think of it like a game of telephone: When a proxy "translates" your HTTP/2 binary frames into HTTP/1.1 text, it must make decisions about how to represent headers, pseudo-headers (like :method, :path), and message boundaries. Different proxies make different choices, creating desynchronization opportunities.

Key Attack Vectors

Header name conflicts: HTTP/2 allows header names that are invalid in HTTP/1.1 (like headers with spaces or uppercase letters). During downgrade, proxies may strip, normalize, or pass these through differently.

Pseudo-header manipulation: Attackers might inject HTTP/1.1 control characters into HTTP/2 pseudo-headers. When downgraded, these can become request smuggling primitives—splitting one request into two at the backend.

Content-Length vs. frame boundaries: HTTP/2 uses frame-based message delimiting, while HTTP/1.1 relies on Content-Length or chunked encoding. Mismatches during translation can cause the backend to read request bodies differently than the frontend intended.

Why It's Dangerous

This attack surface is invisible to traditional request smuggling defenses. Your WAF might validate HTTP/1.1 correctly, and your backend might process HTTP/1.1 safely—but the translation layer creates vulnerabilities neither side can see independently.

Key Takeaway: HTTP/2 downgrade attacks exploit the semantic gap between protocol versions during proxy translation, enabling request smuggling even when both endpoints are individually secure—making the translation layer itself a critical attack surface.