Apache Traffic Server: Out-of-bounds reads while parsing DNS responses

In bta_hd_set_report_act of bta_hd_act.cc, there is a possible out-of-bounds read due to an integer overflow

Some HTTP/2 implementations are vulnerable to a header leak, potentially leading to a denial of service

There are multiple HTTP smuggling and cache poisoning issues when clients making malicious requests interact with Apache Traffic Server (ATS)

Improper Access Control vulnerability in Apache Traffic Server

Improper Access Control vulnerability in Apache Traffic Server

Improper Input Validation vulnerability in Apache Traffic Server

Improper Input Validation vulnerability for the xdebug plugin in Apache Software Foundation Apache Traffic Server can lead to cross site scripting and cache poisoning attacks.This…

Apache Traffic Server: PROXY protocol parsing has port truncation and a stack overflow

Apache Traffic Server: Integer-handling errors in HPACK/XPACK decoding corrupt memory

Apache Traffic Server: Buffer overflow via Host field that has a long string value

Apache Traffic Server: Request smuggling via chunked extension quoted-string parsing

Apache Traffic Server: Regex mappings match with malicious domain names

Improper Check for Unusual or Exceptional Conditions vulnerability in handling the requests to Apache Traffic Server

Pages that are rendered using the ESI plugin can have access to the cookie header when the plugin is configured not to allow access

When there are multiple ranges in a range request, Apache Traffic Server (ATS) will read the entire object from cache

Apache Traffic Server: URL and port parsing errors allow access-control bypass

Apache Traffic Server: HPACK encoder desynchronizes from the decoder after a failed header encode

Apache Traffic Server: HTTP/2 multiplexed origin sessions are reused without certificate re-verification

Expected Behavior Violation vulnerability in Apache Traffic Server