Apache Software Foundation Traffic Server 2.0.0

CPE Details

Apache Software Foundation Traffic Server 2.0.0
apache
traffic_server
2.0.0
2010-09-14
11h41 +00:00
2012-04-02
16h00 +00:00
CPE NVD
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:apache:traffic_server:2.0.0:*:*:*:*:*:*:*

Informations

Vendor

apache

Product

traffic_server

Version

2.0.0

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2019-10079 2019-10-22 13h42 +00:00 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.
7.5
High
CVE-2017-5660 2018-02-27 20h00 +00:00 There is a vulnerability in Apache Traffic Server (ATS) 6.2.0 and prior and 7.0.0 and prior with the Host header and line folding. This can have issues when interacting with upstream proxies and the wrong host being used.
8.6
High
CVE-2017-5659 2017-04-17 16h00 +00:00 Apache Traffic Server before 6.2.1 generates a coredump when there is a mismatch between content length and chunked encoding.
7.5
High
CVE-2014-10022 2015-01-13 11h00 +00:00 Apache Traffic Server before 5.1.2 allows remote attackers to cause a denial of service via unspecified vectors, related to internal buffer sizing.
5
CVE-2014-3525 2014-08-22 12h00 +00:00 Unspecified vulnerability in Apache Traffic Server 3.x through 3.2.5, 4.x before 4.2.1.1, and 5.x before 5.0.1 has unknown impact and attack vectors, possibly related to health checks.
10
CVE-2012-0256 2012-03-26 12h00 +00:00 Apache Traffic Server 2.0.x and 3.0.x before 3.0.4 and 3.1.x before 3.1.3 does not properly allocate heap memory, which allows remote attackers to cause a denial of service (daemon crash) via a long HTTP Host header.
5
CVE-2010-2952 2010-09-13 18h00 +00:00 Apache Traffic Server before 2.0.1, and 2.1.x before 2.1.2-unstable, does not properly choose DNS source ports and transaction IDs, and does not properly use DNS query fields to validate responses, which makes it easier for man-in-the-middle attackers to poison the internal DNS cache via a crafted response.
4.3