HTTP/2 Flow‑Control Exploit Causes Unbounded Memory Growth in Proxygen
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| proxygen | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Proxygen |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.573% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Title | HTTP/2 Flow‑Control Exploit Causes Unbounded Memory Growth in Proxygen | |
| Weaknesses | CWE-399 |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Memory Exhaustion via HTTP/2 Flow‑Control in Proxygen Leading to Denial of Service | |
| Weaknesses | CWE-789 |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Memory Exhaustion via HTTP/2 Flow‑Control in Proxygen Leading to Denial of Service | |
| Weaknesses | CWE-789 |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Facebook
Facebook proxygen |
|
| Vendors & Products |
Facebook
Facebook proxygen |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Proxygen lacked a generalized slow-consumer detection mechanism in its core HTTP session layer. A remote, unauthenticated attacker could exploit HTTP/2 flow-control by setting SETTINGS_INITIAL_WINDOW_SIZE to 0 or withholding WINDOW_UPDATE frames, causing the server to buffer complete response bodies in memory indefinitely for stalled streams. By opening many simultaneous streams requesting large resources while preventing the server from transmitting responses, an attacker could induce unbounded memory growth leading to service degradation, resource exhaustion, or denial of service. Versions v2017.01.16.00 through v2026.07.20.00 are affected. | |
| References |
| |
| Metrics |
cvssV3_1
|