Jakub Zelenka

Encrypting a CMS message to an EC certificate with a group order of 1 can cause the `CMS encrypt()` or `CMS encrypt ex()` functions to loop indefinitely. This occurs because the key generation routine retries without limit while waiting for a nonzero private scalar, which cannot be produced if the group order is 1. An attacker who can provide a recipient certificate with controlled EC parameters to an application performing CMS encryption can trigger this behavior, leading to a Denial of Service by consuming a CPU core until the process is interrupted. The OpenSSL TLS and QUIC implementations are not affected, and FIPS modules in versions 3.0, 3.5, 4.0, and 4.1 are not impacted as they reject arbitrary explicit EC domain parameters.

PHP contains a use-after-free flaw where global state, error handling, object, and extension state may not be correctly reset or may be repopulated after being reset. This occurs because some states point to memory owned by a single request; if a fatal error interrupts the cleanup phase or if the process uses `longjmp()` for out-of-memory (OOM) errors to abort request handling, the global state may refer to memory after it has been freed. Subsequent requests may then read or branch on this stale state before it is fully initialized. An unauthenticated remote attacker can exploit this condition, specifically through the `session.upload progress` component or by sending a specially crafted POST request, to achieve remote code execution (RCE). This issue affects mod php and conditionally affects FPM through application-stage paths.

An unauthenticated remote attacker can achieve remote code execution (RCE) by sending specially crafted HTTP POST requests. The issue resides in the `session.upload progress` component and the memory limit handling during request parsing. PHP uses the `longjmp()` function to handle out-of-memory (OOM) errors to abort request handling; however, some contexts fail to properly account for this, leaving request memory in an uninitialized state. Subsequent cleanup operations may read or branch on this uninitialized memory, leading to memory corruption. Real-world exploitation has been observed against systems using Apache mod php, where attackers used a four-stage HTTP chain to bypass ASLR (Address Space Layout Randomization) via memory disclosure and eventually execute arbitrary commands such as `/bin/sh` to perform reconnaissance and establish reverse callbacks using `curl` and `wget`.

On Windows, filesystem and stream APIs fail to reject reserved device names when they are part of a path. These reserved names include CON, PRN, AUX, NUL, COM1 through COM9, LPT1 through LPT9, CONIN$, and CONOUT$. Consequently, an attacker-controlled filename can reach the `CreateFileW()` function and open a device instead of a standard file. This behavior can lead to a Denial of Service (DoS) by blocking or hanging requests and exhausting worker processes.

The `phar tar number()` function parses the octal size field of a TAR header into a `uint32 t` without an overflow check. Because the field is 11 octal digits wide and can hold values up to 0x1FFFFFFFF, any size exceeding 0xFFFFFFFF silently wraps. This causes the parser to skip an incorrect number of data blocks and interpret attacker-controlled file content as the subsequent TAR header, allowing a crafted archive to inject entries that PharData reports and extracts as genuine.

The FastCGI client access check for IPv6 addresses incorrectly compares only the first 12 bytes of a 16-byte address. This causes the `listen.allowed clients` check to match based on a /96 prefix rather than the exact address. An attacker using an address that shares the first 96 bits with an authorized address can bypass the access control and reach the FastCGI endpoint.

OpenSSL stream peer verification incorrectly handles certificate validation by falling back to the Common Name (CN) when no entries in the `subjectAltName` (SAN) match. According to RFC 6125, the CN should be ignored if the certificate contains any service identity. This behavior allows a certificate trusted for one name to be used to impersonate another if the CN matches the requested `peer name` despite a non-matching DNS SAN.

The `convert.base64-encode`, `convert.quoted-printable-encode`, and `convert.quoted-printable-decode` stream filters contain a memory handling issue. These filters use a `line-break-chars` option where the length is tracked independently of the actual string. The filter constructors use the `pestrdup()` function, which terminates the string at the first NUL byte but retains the original length. Consequently, when the filter generates a line break, it reads beyond the truncated memory allocation, resulting in the leakage of adjacent heap bytes into the filter output.

The mysqlnd wire protocol parser reads fields from server packets without first verifying if the packet contains sufficient bytes. This allows a malicious or compromised MySQL server to send a truncated packet, causing the client to read beyond the packet buffer. This undefined behavior can lead to a process crash.

PHP contains an issue where credentials could be leaked during a redirect when using curl. This occurs when the application follows a redirect to an external host and inadvertently includes authentication credentials in the request to the new location.

The function `php openssl matches wildcard name()` in `ext/openssl/xp ssl.c` contains an integer underflow in the length argument passed to `memchr()`. This occurs when a TLS server certificate uses a wildcard name with literal characters that exceed the length of the hostname being verified. A malicious server can exploit this to force the PHP client to read up to `SIZE MAX` bytes beyond a heap allocation. This issue is reachable via any default client stream as `verify peer name` is enabled by default.

## Vulnerability Report **Name of the Vulnerable Software and Affected Versions** PHP versions 8.1.0 through 8.1.31 PHP versions 8.2.0 through 8.2.27 PHP versions 8.3.0 through 8.3.18 PHP versions 8.4.0 through 8.4.4 PHP 7.4 (Debian) **Description** PHP is an HTML-embedded scripting language commonly used with the Apache HTTP Server. A vulnerability exists in PHP due to a limited location buffer size when parsing HTTP redirects. This can lead to incorrect URL truncation and redirection to a wrong location. **Recommendations** PHP versions 8.1.0 through 8.1.31: Upgrade to version 8.1.32 or later. PHP versions 8.2.0 through 8.2.27: Upgrade to version 8.2.28 or later. PHP versions 8.3.0 through 8.3.18: Upgrade to version 8.3.19 or later. PHP versions 8.4.0 through 8.4.4: Upgrade to version 8.4.5 or later. PHP 7.4 (Debian): Upgrade to a newer version.

The issue is related to the insufficient validation of end-of-line characters in user-supplied headers, which may prevent certain headers from being sent or lead to certain headers being misinterpreted. This can potentially impact the result and lead to denial of service or unexpected issues. The `check has header()` function is specifically mentioned as being related to this issue, where the lack of verification of `r` could lead to misbehavior if only ` ` is used in the header value.

Name of the Vulnerable Software and Affected Versions: PHP versions up to 8.1.31 PHP versions up to 8.2.27 PHP versions up to 8.3.18 PHP versions up to 8.4.4 php7.4 Description: The issue concerns the Streams HTTP Wrapper in PHP. Recommendations: For PHP versions up to 8.1.31, update to a version later than 8.1.31. For PHP versions up to 8.2.27, update to a version later than 8.2.27. For PHP versions up to 8.3.18, update to a version later than 8.3.18. For PHP versions up to 8.4.4, update to a version later than 8.4.4. For php7.4, consider upgrading to a newer version of PHP.