An authentication bypass exists in the `sshd` component when running on Linux systems using musl libc without PAM (Pluggable Authentication Modules). The issue arises from a misinterpretation of whether a string is a password hash. Specifically, when a password exceeding 256 characters is provided, the musl libc `crypt()` function returns a single asterisk (`*`) as an error marker instead of a hash. If a target account is configured as key-only (where the password field in `/etc/shadow` is also an asterisk), OpenSSH compares the error marker to the stored field and mistakenly validates the authentication. This allows an unauthenticated attacker to gain access to such accounts by providing any password between 256 and 1024 characters. This configuration is common in Alpine Linux installations. Successful exploitation can lead to full root access if the affected account has administrative privileges.
A memory corruption issue exists in the PHP core, specifically within the `session.upload progress` component, due to a use-after-free condition. The engine 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 uninitialized before an allocation. Subsequent cleanup procedures may read or branch on this uninitialized memory. An unauthenticated remote attacker can exploit this by sending specially crafted HTTP POST requests to trigger OOM conditions and bypass ASLR, leading to remote code execution (RCE). This is particularly critical for configurations using Apache mod php and PHP-FPM. Real-world exploitation has been observed involving a four-stage HTTP chain that exhausts memory and leaks memory addresses via the `PHPSESSID` header to execute arbitrary shell commands such as `/bin/sh`.
An issue exists in the sshd component when SHA256 or SHA512 are used for user password hashing. When a username does not exist, the system applies BLOWFISH hashing to a static password. This creates a timing difference in response speeds compared to the processing of SHA256 or SHA512 hashes, especially when a large password (approximately 10 KB) is provided. Remote attackers can leverage this timing discrepancy to enumerate valid usernames on the system, which reduces the effort required for subsequent brute-force attacks.