AEGLIX News
A vulnerability in OpenSSH on Linux distributions using the musl C library allows attackers to log into accounts configured to block password authentication by submitting an oversized password, according to research published by BleepingComputer. The flaw, tracked as the sshole vulnerability, affects systems including Alpine Linux, OpenWrt, Buildroot, and Yocto when specific authentication conditions are met, enabling unauthorized access to accounts with a stored asterisk password hash.
The vulnerability stems from how the musl C library's crypt() function handles password hashing failures. When a submitted password exceeds the 256-byte limit, crypt() returns an asterisk, which OpenSSH then compares against a stored asterisk hash in the account's password field, resulting in a successful authentication. Exploitation requires OpenSSH running on a musl-based system with PAM disabled, SSH password authentication enabled, at least one account with an asterisk password hash, and another account with a valid password hash. Systems using glibc, such as Debian, Ubuntu, and Fedora, and those using PAM authentication are not affected. The flaw does not allow bypassing passwords on accounts with valid password hashes.
Researchers discovered the vulnerability using AI agents that conducted approximately 17,600 authentication tests across different OpenSSH configurations, malformed password hashes, and oversized passwords. Alpine Linux official AWS and Azure cloud images ship with a default 'alpine' account that has an asterisk password hash and passwordless 'doas' privileges, which could allow an attacker to escalate to root access if exploited. Administrators can monitor SSH authentication logs for password-based logins to accounts that should not permit them as an indicator of potential exploitation.
The vulnerability has been fixed in OpenSSH 10.6p2. Administrators who cannot update immediately can mitigate the issue by setting PasswordAuthentication to no in the SSH server configuration and restarting the SSH service.
Report prepared 2026-11-05 · Based on reporting from BleepingComputer. Source publication date above; subsequent developments may not be reflected.
Sources
Read original source · BleepingComputer (opens in a new tab)