Traffic Server vulnerabilitiesAnd the versions its exploited flaws hit.
Traffic Server is made by Apache. We track 80 published vulnerabilities in it, across 125 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 10 October 2023. If you run Traffic Server, check your version against the exploited flaws below and patch those first.
The most recent Traffic Server flaw added to the known-exploited list is CVE-2023-44487, on 10 October 2023. We keep watching the known-exploited list.
Which versions of Traffic Server do the exploited flaws hit?
Each exploited flaw lists the versions it affects, usually as ranges. "8.0.0 to before 8.1.9" means from 8.0.0 up to, but not including, 8.1.9. Find your version, then patch.
- CVE-2023-44487Exploited list, 10 Oct 2023
HTTP/2 Rapid Reset Attack Vulnerability
8.0.0 to before 8.1.99.0.0 to before 9.2.3
Which Traffic Server vulnerabilities are being exploited?
1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 7.5HTTP/2 Rapid Reset Attack Vulnerability
HTTP/2 contains a rapid reset vulnerability that allows for a distributed denial-of-service attack (DDoS).
Which Traffic Server flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- >99%
The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.
- 95%CVE-2024-31309High
HTTP/2 CONTINUATION DoS attack can cause Apache Traffic Server to consume more resources on the server.
- 87%CVE-2019-9515High
Some HTTP/2 implementations are vulnerable to a settings flood, potentially leading to a denial of service.
- 83%CVE-2019-9512High
Some HTTP/2 implementations are vulnerable to ping floods, potentially leading to a denial of service.
- 83%CVE-2019-9514High
Some HTTP/2 implementations are vulnerable to a reset flood, potentially leading to a denial of service.
- 82%CVE-2019-9513High
Some HTTP/2 implementations are vulnerable to resource loops, potentially leading to a denial of service.
- 61%CVE-2023-39456High
Improper Input Validation vulnerability in Apache Traffic Server with malformed HTTP/2 frames.This issue affects Apache Traffic Server: from 9.0.0 through 9.2.2.
- 60%CVE-2019-9511High
Some HTTP/2 implementations are vulnerable to window size manipulation and stream prioritization manipulation, potentially leading to a denial of service.
- 28%CVE-2019-9517High
Some HTTP/2 implementations are vulnerable to unconstrained interal data buffering, potentially leading to a denial of service.
Running Traffic Server? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
HTTP/2 contains a rapid reset vulnerability that allows for a distributed denial-of-service attack (DDoS).
- Matched to
- Traffic Server on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 80 published vulnerabilities listed under the name Traffic Server, across 125 versions. The most recent Traffic Server flaw added to the known-exploited list is CVE-2023-44487, on 10 October 2023.
1 is on the list of flaws known to be exploited. The most recently added is CVE-2023-44487.
Each flaw names its own versions, usually as ranges. The newest, CVE-2023-44487, affects 8.0.0 to before 8.1.9, 9.0.0 to before 9.2.3. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Traffic Server. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.