Skip to content
Brief Security & Trust ·

OpenSSH flaw opens locked accounts on some musl Linux setups

Under specific settings, a 257-to-1024-character password can open an account meant to refuse passwords.

In brief
  • It works only on musl-based systems without PAM, with password logins on, and when another account has a real password. Debian, Ubuntu and Fedora are not affected.
  • BleepingComputer says OpenSSH 10.6p2 fixes it. Admins can also turn off SSH password logins.

BleepingComputer reported on 5 November that researcher Ozgun Kultekin published a flaw he calls "*sshole". It affects OpenSSH servers on musl-based Linux, such as Alpine Linux, OpenWrt, Buildroot and Yocto. Kultekin says a password of 257 to 1024 characters can open an account meant to refuse passwords. He says the bug dates to 2016.

Kultekin says a 2016 OpenSSH change, meant to stop username guessing by reply timing, now checks passwords even for locked accounts, which store an asterisk. Musl's password function also returns an asterisk when it fails, as it does past 256 bytes. OpenSSH sees a match. It works only without PAM (a common Linux login layer), with password logins on, and when another account has a real password. A fresh box with no passwords set is not affected. The sources do not say whether anyone has used it.

A safeguard added in 2016 became the hole because it relied on how another component reports failure. Kultekin says glibc and PAM setups do not reach that comparison. On Alpine's official AWS and Azure images, he says the default "alpine" account has passwordless doas (a tool like sudo). If the other conditions are met, that could give an attacker root. Leaders can ask which images and devices run musl, whether they use PAM, and whether password logins are on. BleepingComputer says OpenSSH 10.6p2 fixes it.

A WebPulse Brief: a short report of an important event, written by the WebPulse Newsroom with AI assistance and checked against the reporting below. When there is more to explain, we follow up with a full story. How we use AI.

Reporting: Ozgun Kultekin (independent security researcher).