apache traffic server 2.1.1 vulnerabilities and exploits

(subscribe to this query)

Apache Traffic Server prior to 2.0.1, and 2.1.x prior to 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 malicious users to poison the inte...

Apache Traffic Server Apache Traffic Server 2.1.0 Apache Traffic Server 2.1.1

Apache Traffic Server 2.0.x and 3.0.x prior to 3.0.4 and 3.1.x prior to 3.1.3 does not properly allocate heap memory, which allows remote malicious users to cause a denial of service (daemon crash) via a long HTTP Host header.

Apache Traffic Server 2.0.0 Apache Traffic Server 2.0.1 Apache Traffic Server 2.1.0 Apache Traffic Server 2.1.1 Apache Traffic Server 2.1.2 Apache Traffic Server 2.1.3 Apache Traffic Server 2.1.4 Apache Traffic Server 2.1.5 Apache Traffic Server 2.1.6 Apache Traffic Server 2.1.7 Apache Traffic Server 2.1.8 Apache Traffic Server 2.1.9

Unspecified vulnerability in Apache Traffic Server 3.x up to and including 3.2.5, 4.x prior to 4.2.1.1, and 5.x prior to 5.0.1 has unknown impact and attack vectors, possibly related to health checks.

Apache Traffic Server 2.0.0 Apache Traffic Server 2.0.1 Apache Traffic Server 2.1.0 Apache Traffic Server 2.1.1 Apache Traffic Server 2.1.2 Apache Traffic Server 2.1.3 Apache Traffic Server 2.1.4 Apache Traffic Server 2.1.5 Apache Traffic Server 2.1.6 Apache Traffic Server 2.1.7 Apache Traffic Server 2.1.8 Apache Traffic Server 2.1.9

Vulmon Search is a vulnerability search engine. It gives comprehensive vulnerability information through a very simple user interface.

Home Recent Vulnerabilities Product List Vendor List Research Posts Trends Blog About Contact

Vulmon Search Vulmon Research Vulmon Alerts Vulmap

Twitter Reddit Linkedin Facebook