OpenSSH Releases Urgent Workaround for Alpine Password Bypass Vulnerability

iconThe Defiant
Share
AI summary iconSummary
OpenSSH released version 10.6p2 on Nov. 5 to fix a critical vulnerability news affecting Alpine Linux servers. The flaw allowed attackers to bypass passwords on systems using the musl C library with PAM disabled. Alpine Linux urged users to update and restart SSH or disable password authentication. The on-chain news highlights the need for immediate action to secure infrastructure. Operators are advised to apply the patch without delay.

OpenSSH released version 10.6p2 on Nov. 5 to work around a critical flaw that lets attackers log into some Alpine Linux servers without knowing a password.

The release notes identify Linux systems using the musl C library with PAM, a password-authentication framework, disabled. OpenSSH developer Damien Miller urged operators to disable password authentication or SSH itself “IMMEDIATELY.” He said Linux systems using glibc, systems using PAM for password authentication and non-Linux systems are unaffected.

Alpine's advisory tells operators to update and restart the SSH server, sshd: installing the package alone leaves the old server process running. Operators unable to update should set PasswordAuthentication no and restart it, first checking that key-based login works and keeping their existing session open while testing a new login.

For crypto node, validator and exchange operators, the relevant exposure is the remote-login service, not simply an Alpine-based container. Alpine says containers that do not run sshd are unaffected. But an account intended for key-only access can still be exposed if the server continues to accept password logins.

How Key-Only Accounts Become Exposed

According to Alpine, exploitation requires a reachable SSH server with password authentication enabled and PAM disabled. Alpine's standard openssh-server package is built without PAM; its PAM-enabled alternative is also exposed when configured with UsePAM no.

The attacker must know the name of a login-eligible account whose stored password field is an asterisk, and the machine must also contain an account with a SHA-256 or SHA-512 password hash. Alpine says a password attempt of 257 to 1,024 bytes can then authenticate without the correct password.

Alpine traces the failure to password checking: musl's hashing function returns an asterisk as an error indicator for an overlong password. That can match the asterisk stored for an account with no password. The default restriction on root password logins still protects root unless an operator has changed it to allow those logins.

Cloud-image exposure also depends on configuration. Alpine says its unpatched official tiny-cloud images from 3.18.11 through 3.24.3 are safe on first boot, but become exploitable if a SHA-512 password hash is added. In that case, an attacker can enter as the alpine user and elevate to root using its passwordless administrative privileges. Images built from 3.21.10, 3.22.8, 3.23.8 and 3.24.4 include the fix. Images configured through cloud-init, which disables SSH password authentication, are unaffected.

OpenSSH describes 10.6p2 as a workaround and places the root cause outside its server software. Musl's main author and maintainer, Rich Felker, said his position is that “it is not a musl vulnerability.”

Backported Fixes for Older Alpine Branches

Alpine has released updated images and published patched OpenSSH packages for branches back to 3.16. Older branches carry backported fixes rather than the upstream 10.6p2 version number.

The advisory lists these fixed packages:

Alpine BranchFixed OpenSSH Package
edge10.6_p2-r0
3.2410.3_p1-r2
3.2310.2_p1-r1
3.2210.0_p1-r11
3.219.9_p2-r1
3.209.7_p1-r6
3.199.6_p1-r3
3.189.3_p2-r4
3.179.1_p1-r7
3.169.0_p1-r6

For potentially exposed machines, Alpine advises reviewing logs for accepted password logins to accounts with no password. If an unauthorized login cannot be ruled out, it says to treat the machine as compromised.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.