Haruki Oyama

Apache Traffic Server is susceptible to request smuggling, a technique where an attacker interferes with the way a website and its proxy server process sequences of HTTP requests, when chunked messages are malformed.

An issue exists when the software is configured with `serve-expired: yes` and `serve-expired-client-timeout` is greater than `discard-timeout` (where `discard-timeout` is greater than 0). In this specific configuration, the `discard-timeout` branch within the serve expired logic drops an aged client reply without correctly decrementing the counter for the number of reply addresses for the query. Because the counter is not decremented, it can reach its maximum limit, causing new clients for duplicate in-flight queries to be silently dropped, which leads to a degradation of the resolution service. A malicious actor can trigger this by querying the resolver for a client-controlled slow-on-demand authoritative zone to push the counter past the threshold.

A memory corruption flaw exists when handling APL (Address Prefix List) resource records during the process of serializing or writing a zone to disk. The issue stems from improper input validation and bounds checking of the `adflength` field. An attacker can trigger a stack-based buffer overflow by introducing a specially crafted APL record with an `adflength` larger than permitted for the address family into a zone. This can result in the overwrite of up to 111 attacker-controlled bytes on the stack, potentially leading to a denial of service or arbitrary code execution.

The X25519 x86 64 assembly implementation fails to clear the most significant bit during the final modular reduction. This occurs because the final carry-propagation chains in the x64 and AVX2 reduction routines could overflow into the top bit, and the high limb was not masked afterward. Consequently, the computed result may not be fully reduced modulo the field prime 2^255 - 19, leaving the field element in a non-canonical form. This can lead to incorrect results from scalar multiplication and potentially the generation of an incorrect shared secret.

An attacker can send a large volume of crafted DNS queries to trigger the insertion of a dynamic block. This action results in the production of invalid output at the prometheus endpoint, causing the scraper to reject the endpoint until the dynamic block expires.

A flaw exists in the `extractall()` function when using the 'data' or 'tar' filters. A specially crafted archive containing a hardlink that references a symlink stored at a deeper path can bypass these filters. The extraction process validates the symlink at its original archived location but recreates it at the shallower path of the hardlink. This allows a relative target to escape the destination directory, enabling a malicious archive to create symlinks that point outside the intended folder, which can lead to unauthorized file reads or writes outside the destination.

A heap out-of-bounds read can occur during CMS password-based decryption (RFC 3211 / PWRI key unwrap) when processing attacker-supplied CMS data. The issue arises in the `kek unwrap key()` function when an attacker selects a stream-mode Key Encryption Key (KEK) cipher via an OID in the `keyEncryptionAlgorithm`. Because the system does not require the cipher to be a block cipher, the minimum length check is bypassed, allowing the allocated buffer for the unwrapped key to be too small for the RFC-specified check-bytes. This can lead to a crash and subsequent Denial of Service if the input buffer ends at a memory page boundary and the following page is unmapped. Applications using `CMS decrypt()` or `CMS decrypt set1 password()` on untrusted data are affected. No password knowledge is required to trigger this issue. FIPS modules are not affected.

The Keycloak authentication manager fails to generate or validate the OAuth 2.0 `state` parameter during the login and login-callback flow and does not implement PKCE (Proof Key for Code Exchange), a security extension to OAuth 2.0 that prevents authorization code injection. An attacker with a Keycloak account in the same realm can deliver a crafted callback URL to a victim's browser, forcing the victim to be logged into the attacker's Airflow session. This login-CSRF or session fixation allows the attacker to harvest any credentials the victim subsequently stores in Airflow Connections.

Name of the Vulnerable Software and Affected Versions Apache Tomcat versions 11.0.0-M14 through 11.0.20, versions 10.1.22 through 10.1.53, and versions 9.0.92 through 9.0.116 Description CLIENT CERT authentication may not fail as expected in certain scenarios when soft fail is disabled and FFM is used. Recommendations Upgrade to version 11.0.21 Upgrade to version 10.1.54 Upgrade to version 9.0.117

HTTP response splitting occurs in multiple Apache HTTP Server modules when interacting with untrusted or compromised backend servers. This issue allows an attacker to split an HTTP response, potentially leading to cache poisoning or cross-site scripting.

A flaw exists where hostname verification is ignored when configured through the `verifyHostName` attribute of the '<Ssl>' element. This occurs even if the attribute is explicitly set, leaving TLS connections susceptible to interception. A network-based attacker could perform a man-in-the-middle attack if an SMTP, Socket, or Syslog appender is used, TLS is configured via a nested '<Ssl>' element, and the attacker possesses a certificate issued by a CA trusted by the configured or default Java trust store.