Accounts intended to reject passwords can admit remote attackers on certain Linux systems. The issue affects OpenSSH before 10.6p2 when musl is used without PAM and account settings rely on an asterisk to block password login. An oversized password can trigger a matching error value and be accepted. Alpine Linux and some other musl-based distributions can be exposed under these conditions.
What Happened
A password authentication bypass affects OpenSSH versions before 10.6p2 on Linux systems that use the musl C library without PAM under specific account configurations. The issue can allow an attacker to log in with a password to an account that was configured not to accept password authentication.
Linux administrators can disable password use for an account by placing an asterisk in the password field within the shadow password file. The asterisk is not a usable password hash, so no valid password should match it. OpenSSH nevertheless performs password hashing for these accounts as part of behavior introduced in 2016 to reduce username enumeration through timing differences.
The problem arises from the interaction with musl. Its password-hashing function can return an asterisk when processing fails, including when a submitted password is too long. OpenSSH can then compare that returned error value with the asterisk stored for the disabled account and treat them as matching. The vulnerability summary says passwords between 256 and 1024 characters can succeed under the affected conditions.
The issue applies to musl-based environments such as Alpine Linux and can also affect systems built with OpenWrt, Buildroot or Yocto when the required configuration is present. It does not bypass accounts that have valid password hashes. Systems using glibc, including Debian, Ubuntu and Fedora, are not affected through this path, and configurations using PAM are also outside the reported conditions. The issue was fixed in OpenSSH 10.6p2.
Why It Matters
The main risk is a false sense of protection. An administrator may see an asterisk in an account’s password field and reasonably believe that password login is impossible. Under the vulnerable combination of OpenSSH, musl and authentication settings, the component used to validate the password can produce the same value that represents a disabled account.
The exposure may be easy to miss because musl-based systems often appear in cloud images, network appliances, containers and embedded environments rather than standard enterprise server fleets. The researcher warned that official Alpine Linux images for AWS and Azure include a default alpine account with passwordless doas privileges. If that account is reachable through an affected SSH configuration, successful login could provide a route to elevated access.
This is not a universal OpenSSH bypass. Exposure depends on the operating system library, lack of PAM, OpenSSH version and account configuration. That makes accurate asset and configuration data essential for prioritization.
What to Watch
Defenders should look for successful password-based SSH logins involving accounts that were intended to reject passwords. On Alpine Linux, particular attention should go to the alpine account and any other account whose stored password field contains an asterisk.
Teams should also identify public-facing SSH services running on musl-based systems and determine whether password authentication remains enabled. Appliances and embedded products deserve review because their underlying Linux distribution and authentication stack may not be obvious from normal inventory records.
After updating, organizations should confirm that the installed OpenSSH package contains the 10.6p2 correction and that the service restarted successfully. Any unexpected successful login to a disabled account should lead to a broader investigation of activity performed through that session.
What Defenders Should Do
Update affected systems to OpenSSH 10.6p2 or the corrected package supplied by the relevant distribution. Alpine Linux administrators can update the OpenSSH packages through the normal package upgrade process. Prioritize hosts that are reachable from untrusted networks, contain privileged disabled accounts or use official cloud images with the default alpine account.
Where an immediate update is not possible, turn off SSH password authentication by setting PasswordAuthentication no in the SSH server configuration and restarting the service. Confirm that administrators retain a tested alternative access method before making the change. Do not rely only on the asterisk in the account’s password field as proof that SSH password login is blocked.
Review authentication logs for successful password logins to accounts that should not accept passwords. If such a login is found, examine the account’s stored password state and investigate subsequent commands, privilege use and network activity. Inventory work should include Alpine Linux, OpenWrt, Buildroot and Yocto-based systems, while confirming whether each device actually uses musl without PAM and has the vulnerable OpenSSH behavior.
The Larger Lesson
Security controls can break at the boundary between components. OpenSSH treated an asterisk as an unusable stored password, while musl could return the same character as an error result. Each behavior had a purpose, but their interaction produced an authentication bypass.
The broader lesson is to validate the complete authentication path rather than infer protection from one configuration value. Libraries, operating-system choices and account defaults can change how a security setting behaves in practice, especially in cloud images and embedded systems.
