Apache Traffic Server is vulnerable to HTTP/2 setting flood attacks.

published 2019-10-22 7y ago modified 2026-06-17 4mo ago also EUVD-2019-2134

cvss: 7.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 4.6%; EPSS 4.6% chance of exploitation in 30 days, percentile 91%
public exploits: 0; none known

Apache Traffic Server is vulnerable to HTTP/2 setting flood attacks. Earlier versions of Apache Traffic Server didn't limit the number of setting frames sent from the client using the HTTP/2 protocol. Users should upgrade to Apache Traffic Server 7.1.7, 8.0.4, or later versions.

Patch / fix

fixed in 1 distros 1

apache traffic_server 7.1.7, 8.0.4

trafficserver Debian 12 8.0.5+ds-1

debian advisories DEBIAN-CVE-2019-10079

Is CVE-2019-10079 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

4.56% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:N/A:P

Affected products

n/a Apache Traffic Server

Classification

Weakness

CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

CVE List CVE-2019-10079
NVD CVE-2019-10079

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.