Technology1 min read

sshhole: OpenSSH musl Password Bypass on Alpine and OpenWrt

By · Via Lemmy Technology · Published by Everything Blog

In short

The vulnerability allows any password between 257 and 1024 characters to be accepted for accounts with a password field set to an asterisk in the shadow file. This primarily impacts accounts intended to be locked, such as certain LDAP-mapped profiles and Alpine cloud root logins. Systems running glibc, configurations utilizing PAM, OpenBSD, and Dropbear SSH servers remain completely unaffected. OpenSSH rolled out a workaround in version 10.6p2 alongside backported fixes issued by Alpine.

Key points

  • Deployments using glibc or configured with PAM enabled are safe from this authentication…: Deployments using glibc or configured with PAM enabled are safe from this authentication bypass.
  • Alpine has backported essential security patches to both active branches and several end-…: Alpine has backported essential security patches to both active branches and several end-of-life releases.
  • Systems that rely strictly on the Dropbear SSH server are completely unaffected by this v…: Systems that rely strictly on the Dropbear SSH server are completely unaffected by this vulnerability.

Sources checked by our analysis pipeline: 1

OpenSSH built against musl libc and running without PAM accepts any password between 257 and 1024 characters for accounts whose password field in /etc/shadow is exactly *. The accounts affected are those intentionally locked or configured for key-only authentication, including root on many Alpine cloud images, deploy users, and certain LDAP-mapped accounts.

The condition is present only on musl-based systems that do not use PAM for password verification. glibc systems, systems with UsePAM yes, Dropbear, and OpenBSD are unaffected. OpenSSH 10.6p2, released 5 November 2026, contains a workaround. Alpine has backported the fix across supported and several EOL branches.

You must log in or register to comment.

Technology