Apache Traffic Server drops the per-stream buffer cap
Summary
Apache Traffic Server drops the per-stream buffer cap when dechunking HTTP/2 or HTTP/3 responses, letting a slow client exhaust server memory. This issue affects Apache Traffic Server: from 8.0.0 through 8.1.9, from 9.0.0 through 9.2.14, from 10.0.0 through 10.1.3. Users are recommended to upgrade to version 9.2.15 or 10.1.4, which fix the issue.
What this means
In plain English
Apache Traffic Server drops the per-stream buffer cap when dechunking HTTP/2 or HTTP/3 responses, letting a slow client exhaust server memory. This issue affects Apache Traffic Server: from 8.0.0 through 8.1.9, from 9.0.0 through 9.2.14, from 10.0.0 through 10.1.3. Users are recommended to upgrade to version 9.2.15 or 10.1.4, which fix the issue.
Vulnerable items
- Apache Traffic Server — Apache Traffic Server is a Apache Software Foundation server component identified as affected by the official advisory.
Recommended action
Primary action: update to a vendor-listed fixed release: 9.2.15, 10.1.4. Vendor mitigation: Users are recommended to upgrade to version 9.2.15 or 10.1.4, which fix the issue.
Rewritten locally from the scraped official advisory data above; no generative API is used. The vendor advisory is authoritative.
- 8.0.0 through 8.1.9
- 9.0.0 through 9.2.14
- 10.0.0 through 10.1.3.
- through 10.1.3
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
- 9.2.15
- 10.1.4
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Mitigation checklist
- Users are recommended to upgrade to version 9.2.15 or 10.1.4, which fix the issue.
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.