Vulnerabilities

OpenSSH Flaw Lets Attackers Log Into Some Password-Locked Linux Accounts

A flaw disclosed Nov. 5 affects certain OpenSSH setups using musl. A fix is out in OpenSSH 10.6p2, and Alpine Linux admins should check their servers.

OpenSSH Flaw Lets Attackers Log Into Some Password-Locked Linux Accounts

Certain OpenSSH configurations on systems built with the musl library allow password login to accounts that were never supposed to accept it. Details of the issue, dubbed *sshole, were published on November 5. A fix is available in OpenSSH 10.6p2.

Who is affected

Researcher Ozgun Kultekin says the flaw requires several conditions to line up: the system uses musl, PAM is disabled, SSH password authentication is enabled, and the account has a * character in its password field. Another account with a valid password hash must also exist. Running Alpine Linux or OpenWrt does not by itself mean that a particular device is vulnerable.

The problem lies in how errors in password hash computation are handled. The value the library returns can be wrongly treated as matching the marker that is meant to lock the account. Accounts with valid password hashes cannot be bypassed this way. The researcher’s write-up also points to a risk involving the default user in the official Alpine images for AWS and Azure, which has privilege escalation rights.

What to do now

Administrators should pair the update with a check of how the service is actually configured. We recommend the following order:

  • Identify which servers and devices run OpenSSH with the musl library. Include cloud images and custom-built systems.
  • Install the patched package from your distribution. For Alpine, the recommended command is apk upgrade openssh.
  • If the update has to wait, disable password login by setting PasswordAuthentication no and reload the service according to your administrative procedures.
  • Before making the change, confirm that key-based access works and make sure you can recover the connection from the console.
  • Review successful password logins to accounts that should accept keys only. Preserve any suspicious entries for analysis.

Verification should cover the running service and its effective settings. Editing the configuration file without the process actually applying the change does not confirm that the risk is gone.

SecurHUB’s take

The assumption that an account has no usable password is worth verifying across the entire authentication path. Security audits help review the configuration of administrative access and the privileges of service accounts.

Sources: Ozgun Kultekin, BleepingComputer

AuthorSecurHUB Team

Read more

Related articles

Want to know if this affects your company?

A free consultation with one of our experts — no obligation, in full confidence.

Let's talk