Masaori Koshiba

Apache Traffic Server can crash with a null pointer dereference when a client POST request is torn down via half-close while a chunked origin response is being reparsed from a reentrant write-ready callback, a timing-dependent race introduced by the CVE-2021-32564 flow-control backports. This issue affects Apache Traffic Server: 9.2.15, 10.1.4, 10.2.0. Users are recommended to upgrade to version 9.2.16, 10.1.5, or 10.2.1, which fix the issue.

**اسم البرنامج المعرض للخطر والإصدارات المتأثرة** إصدارات Apache Traffic Server من 9.2.0 إلى 9.2.8 إصدارات Apache Traffic Server من 10.0.0 إلى 10.0.3 **الوصف** تتعلق المشكلة بوجود خلل في التحكم في الوصول في Apache Traffic Server. **التوصيات** بالنسبة للإصدارات من 9.2.0 إلى 9.2.8، قم بالتحديث إلى الإصدار 9.2.9. بالنسبة للإصدارات من 10.0.0 إلى 10.0.3، قم بالتحديث إلى الإصدار 10.0.4.

**Name of the Vulnerable Software and Affected Versions** Apache Traffic Server version 9.1.0 **Description** The issue is related to a buffer copy without checking the size of input, also known as a 'Classic Buffer Overflow', in the stats-over-http plugin of Apache Traffic Server. This allows a remote attacker to overwrite memory, potentially leading to a denial of service. **Recommendations** For Apache Traffic Server version 9.1.0, consider disabling the stats-over-http plugin as a temporary workaround until a patch is available. Restrict access to the vulnerable plugin to minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Apache Traffic Server versions 7.0.0 through 7.1.12 Apache Traffic Server versions 8.0.0 through 8.1.1 Apache Traffic Server versions 9.0.0 through 9.0.1 **Description** The issue is related to improper input validation in the HTTP/2 module of Apache Traffic Server, which can be exploited by an attacker to cause a denial of service (DOS) of the server. **Recommendations** For versions 7.0.0 through 7.1.12, update to a version outside of this range to resolve the issue. For versions 8.0.0 through 8.1.1, update to a version outside of this range to resolve the issue. For versions 9.0.0 through 9.0.1, update to a version outside of this range to resolve the issue. As a temporary workaround, consider restricting access to the HTTP/2 module until a patch is available.

**Name of the Vulnerable Software and Affected Versions** Apache Traffic Server versions 7.0.0 through 7.1.12 Apache Traffic Server versions 8.0.0 through 8.1.1 Apache Traffic Server versions 9.0.0 through 9.0.1 **Description** The issue is caused by a stack-based buffer overflow in the cachekey plugin of Apache Traffic Server. This can allow a remote attacker to impact the confidentiality, integrity, and availability of protected information. **Recommendations** For Apache Traffic Server versions 7.0.0 through 7.1.12, update to a version outside of this range to resolve the issue. For Apache Traffic Server versions 8.0.0 through 8.1.1, update to a version outside of this range to resolve the issue. For Apache Traffic Server versions 9.0.0 through 9.0.1, update to a version outside of this range to resolve the issue. As a temporary workaround, consider disabling the cachekey plugin until a patch is available.

**Name of the Vulnerable Software and Affected Versions** Apache ATS versions 6.0.0 through 6.2.3 Apache ATS versions 7.0.0 through 7.1.9 Apache ATS versions 8.0.0 through 8.0.6 **Description** The issue is related to a HTTP/2 slow read attack and a reverse proxy and proxy redirection vulnerability in the Apache Traffic Server, which can lead to uncontrolled resource consumption. Exploitation of this issue may allow a remote attacker to cause a denial of service. **Recommendations** For versions 6.0.0 through 6.2.3, update to a version outside of this range to resolve the issue. For versions 7.0.0 through 7.1.9, update to a version outside of this range to resolve the issue. For versions 8.0.0 through 8.0.6, update to a version outside of this range to resolve the issue. As a temporary workaround, consider restricting access to the HTTP/2 protocol until a patch is available.