Apache Traffic Server
stack.watch can notify you when security vulnerabilities are reported in Apache Traffic Server. You can add multiple products that you use with Traffic Server to create your own personal software stack watcher.
By the Year
In 2020 there have been 5 vulnerabilities in Apache Traffic Server with an average score of 8.9 out of ten. Last year Traffic Server had 10 security vulnerabilities published. Right now, Traffic Server is on track to have less security vulerabilities in 2020 than it did last year. However, the average CVE base score of the vulnerabilities in 2020 is greater by 1.38.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2020 | 5 | 8.88 |
| 2019 | 10 | 7.50 |
| 2018 | 5 | 6.42 |
It may take a day or so for new Traffic Server vulnerabilities to show up. Additionally vulnerabilities may be tagged under a different product or component name.
Latest Apache Traffic Server Security Vulnerabilities
Apache Traffic Server 6.0.0 to 6.2.3
CVE-2020-9494
7.5 - High
- June 24, 2020
Apache Traffic Server 6.0.0 to 6.2.3, 7.0.0 to 7.1.10, and 8.0.0 to 8.0.7 is vulnerable to certain types of HTTP/2 HEADERS frames that can cause the server to allocate a large amount of memory and spin the thread.
Memory Corruption
Apache ATS 6.0.0 to 6.2.3
CVE-2020-9481
7.5 - High
- April 27, 2020
Apache ATS 6.0.0 to 6.2.3, 7.0.0 to 7.1.9, and 8.0.0 to 8.0.6 is vulnerable to a HTTP/2 slow read attack.
Uncontrolled Resource Consumption ('Resource Exhaustion')
There is a vulnerability in Apache Traffic Server 6.0.0 to 6.2.3
CVE-2020-1944
9.8 - Critical
- March 23, 2020
There is a vulnerability in Apache Traffic Server 6.0.0 to 6.2.3, 7.0.0 to 7.1.8, and 8.0.0 to 8.0.5 with a smuggling attack and Transfer-Encoding and Content length headers. Upgrade to versions 7.1.9 and 8.0.6 or later versions.
Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling')
There is a vulnerability in Apache Traffic Server 6.0.0 to 6.2.3
CVE-2019-17559
9.8 - Critical
- March 23, 2020
There is a vulnerability in Apache Traffic Server 6.0.0 to 6.2.3, 7.0.0 to 7.1.8, and 8.0.0 to 8.0.5 with a smuggling attack and scheme parsing. Upgrade to versions 7.1.9 and 8.0.6 or later versions.
Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling')
There is a vulnerability in Apache Traffic Server 6.0.0 to 6.2.3
CVE-2019-17565
9.8 - Critical
- March 23, 2020
There is a vulnerability in Apache Traffic Server 6.0.0 to 6.2.3, 7.0.0 to 7.1.8, and 8.0.0 to 8.0.5 with a smuggling attack and chunked encoding. Upgrade to versions 7.1.9 and 8.0.6 or later versions.
Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling')
Apache Traffic Server is vulnerable to HTTP/2 setting flood attacks
CVE-2019-10079
7.5 - High
- October 22, 2019
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.
Improper Input Validation
Some HTTP/2 implementations are vulnerable to window size manipulation and stream prioritization manipulation
CVE-2019-9511
7.5 - High
- August 13, 2019
Some HTTP/2 implementations are vulnerable to window size manipulation and stream prioritization manipulation, potentially leading to a denial of service. The attacker requests a large amount of data from a specified resource over multiple streams. They manipulate window size and stream priority to force the server to queue the data in 1-byte chunks. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both.
Uncontrolled Resource Consumption ('Resource Exhaustion')
Some HTTP/2 implementations are vulnerable to ping floods
CVE-2019-9512
7.5 - High
- August 13, 2019
Some HTTP/2 implementations are vulnerable to ping floods, potentially leading to a denial of service. The attacker sends continual pings to an HTTP/2 peer, causing the peer to build an internal queue of responses. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both.
Uncontrolled Resource Consumption ('Resource Exhaustion')
Some HTTP/2 implementations are vulnerable to resource loops
CVE-2019-9513
7.5 - High
- August 13, 2019
Some HTTP/2 implementations are vulnerable to resource loops, potentially leading to a denial of service. The attacker creates multiple request streams and continually shuffles the priority of the streams in a way that causes substantial churn to the priority tree. This can consume excess CPU.
Uncontrolled Resource Consumption ('Resource Exhaustion')
Some HTTP/2 implementations are vulnerable to a reset flood
CVE-2019-9514
7.5 - High
- August 13, 2019
Some HTTP/2 implementations are vulnerable to a reset flood, potentially leading to a denial of service. The attacker opens a number of streams and sends an invalid request over each stream that should solicit a stream of RST_STREAM frames from the peer. Depending on how the peer queues the RST_STREAM frames, this can consume excess memory, CPU, or both.
Uncontrolled Resource Consumption ('Resource Exhaustion')
Some HTTP/2 implementations are vulnerable to a settings flood
CVE-2019-9515
7.5 - High
- August 13, 2019
Some HTTP/2 implementations are vulnerable to a settings flood, potentially leading to a denial of service. The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame is almost equivalent in behavior to a ping. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both.
Uncontrolled Resource Consumption ('Resource Exhaustion')
Some HTTP/2 implementations are vulnerable to a header leak
CVE-2019-9516
7.5 - High
- August 13, 2019
Some HTTP/2 implementations are vulnerable to a header leak, potentially leading to a denial of service. The attacker sends a stream of headers with a 0-length header name and 0-length header value, optionally Huffman encoded into 1-byte or greater headers. Some implementations allocate memory for these headers and keep the allocation alive until the session dies. This can consume excess memory.
Uncontrolled Resource Consumption ('Resource Exhaustion')
Some HTTP/2 implementations are vulnerable to unconstrained interal data buffering
CVE-2019-9517
7.5 - High
- August 13, 2019
Some HTTP/2 implementations are vulnerable to unconstrained interal data buffering, potentially leading to a denial of service. The attacker opens the HTTP/2 window so the peer can send without constraint; however, they leave the TCP window closed so the peer cannot actually write (many of) the bytes on the wire. The attacker then sends a stream of requests for a large response object. Depending on how the servers queue the responses, this can consume excess memory, CPU, or both.
Uncontrolled Resource Consumption ('Resource Exhaustion')
Some HTTP/2 implementations are vulnerable to a flood of empty frames
CVE-2019-9518
7.5 - High
- August 13, 2019
Some HTTP/2 implementations are vulnerable to a flood of empty frames, potentially leading to a denial of service. The attacker sends a stream of frames with an empty payload and without the end-of-stream flag. These frames can be DATA, HEADERS, CONTINUATION and/or PUSH_PROMISE. The peer spends time processing each frame disproportionate to attack bandwidth. This can consume excess CPU.
Uncontrolled Resource Consumption ('Resource Exhaustion')
sslheaders plugin extracts information
CVE-2018-11783
7.5 - High
- March 07, 2019
sslheaders plugin extracts information from the client certificate and sets headers in the request based on the configuration of the plugin. The plugin doesn't strip the headers from the request in some scenarios. This problem was discovered in versions 6.0.0 to 6.0.3, 7.0.0 to 7.1.5, and 8.0.0 to 8.0.1.
Information Leak
Adding method ACLs in remap.config can cause a segfault when the user makes a carefully crafted request. This affects versions Apache Traffic Server (ATS) 6.0.0 to 6.2.2 and 7.0.0 to 7.1.3. To resolve this issue users running 6.x should upgrade to 6.2.3 or later versions and 7.x users should upgrade to 7.1.4 or later versions
CVE-2018-1318
7.5 - High
- August 29, 2018
Adding method ACLs in remap.config can cause a segfault when the user makes a carefully crafted request. This affects versions Apache Traffic Server (ATS) 6.0.0 to 6.2.2 and 7.0.0 to 7.1.3. To resolve this issue users running 6.x should upgrade to 6.2.3 or later versions and 7.x users should upgrade to 7.1.4 or later versions.
Improper Input Validation
There are multiple HTTP smuggling and cache poisoning issues when clients making malicious requests interact with Apache Traffic Server (ATS). This affects versions 6.0.0 to 6.2.2 and 7.0.0 to 7.1.3. To resolve this issue users running 6.x should upgrade to 6.2.3 or later versions and 7.x users should upgrade to 7.1.4 or later versions
CVE-2018-8004
6.5 - Medium
- August 29, 2018
There are multiple HTTP smuggling and cache poisoning issues when clients making malicious requests interact with Apache Traffic Server (ATS). This affects versions 6.0.0 to 6.2.2 and 7.0.0 to 7.1.3. To resolve this issue users running 6.x should upgrade to 6.2.3 or later versions and 7.x users should upgrade to 7.1.4 or later versions.
Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling')
When there are multiple ranges in a range request, Apache Traffic Server (ATS) will read the entire object
CVE-2018-8005
5.3 - Medium
- August 29, 2018
When there are multiple ranges in a range request, Apache Traffic Server (ATS) will read the entire object from cache. This can cause performance problems with large objects in cache. This affects versions 6.0.0 to 6.2.2 and 7.0.0 to 7.1.3. To resolve this issue users running 6.x users should upgrade to 6.2.3 or later versions and 7.x users should upgrade to 7.1.4 or later versions.
Uncontrolled Resource Consumption ('Resource Exhaustion')
A carefully crafted invalid TLS handshake can cause Apache Traffic Server (ATS) to segfault
CVE-2018-8022
7.5 - High
- August 29, 2018
A carefully crafted invalid TLS handshake can cause Apache Traffic Server (ATS) to segfault. This affects version 6.2.2. To resolve this issue users running 6.2.2 should upgrade to 6.2.3 or later versions.
Improper Input Validation
Pages that are rendered using the ESI plugin can have access to the cookie header when the plugin is configured not to
CVE-2018-8040
5.3 - Medium
- August 29, 2018
Pages that are rendered using the ESI plugin can have access to the cookie header when the plugin is configured not to allow access. This affects Apache Traffic Server (ATS) versions 6.0.0 to 6.2.2 and 7.0.0 to 7.1.3. To resolve this issue users running 6.x should upgrade to 6.2.3 or later versions and 7.x users should upgrade to 7.1.4 or later versions.
Exposure of Resource to Wrong Sphere