Haruki Oyama

**Name of the Vulnerable Software and Affected Versions** OpenSSL (affected versions not specified) **Description** 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. **Recommendations** 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-airflow-providers-keycloak versions prior to 0.7.0 **Description** 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. **Recommendations** Upgrade to version 0.7.0 or later.

**Name of the Vulnerable Software and Affected Versions** Apache Log4j Core versions 2.12.0 through 2.25.3 **Description** 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. **Recommendations** Upgrade to Apache Log4j Core 2.25.4.

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

**Name of the Vulnerable Software and Affected Versions** Apache HTTP Server versions prior to 2.4.67 **Description** 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. **Recommendations** Upgrade to version 2.4.67.