Alpine Linux tiny-cloud images SSH Bypass Vulnerability
Alpine Linux has disclosed that its official tiny-cloud images from versions 3.18.11 through 3.24.3 are susceptible to an OpenSSH login bypass, allowing an attacker who can reach SSH to use an unusually long password to access certain passwordless accounts (like the alpine account), which can then escalate to root via passwordless doas. The vulnerability only becomes exploitable after a SHA-512 password hash (
$5$or$6$) exists on the system—such as after setting a console password or adding a user with a hashed password—and requires password authentication enabled, a non-PAM sshd configuration, and an account with a*password field. Affected images are fixed in point releases 3.21.10, 3.22.8, 3.23.8, and 3.24.4; existing instances should update or disable password authentication. Systems without sshd, those usingPasswordAuthentication no, oropenssh-server-pamwithUsePAM yesare not affected.
A Conveniently Oversized Key
They call it a "bug," but ask yourself: what kind of accident produces a master key exactly when and where the global cloud architecture needs one? The article admits that this OpenSSH login bypass appears across an entire range of official Alpine images—from 3.18.11 through 3.24.3—allowing an attacker with an "unusually long password" to slide into passwordless accounts. In the real world, a password that is too long behaves like a skeleton key, and a skeleton key is never a mistake. It is a design choice made by people who understand that while you are busy setting up your tiny-cloud infrastructure, they are laying a pliant backdoor into the very foundation. Note the condition: the bypass only activates once a SHA-512 password hash lands on the machine. That is not a random technical detail; that is a signal. The machine is now "real" enough to be entered.
The Hash That Opens Every Door
Consider the geometry of control: one account on that Alpine image with a $5$ or $6$ hash, and suddenly every passwordless account is uncovered. The passwordless accounts are the invisible ones—the root-level actors who leave no trace, who were never supposed to be categorized. The hashed account is the front man, the financier, the foundation grant that legitimizes a network of shell entities. This is exactly how the Managing Class operates: manufacture one visible, credentialed identity, then use it to reach into all the shadow accounts that surround it. And notice where this vulnerability resides: in Alpine's tiny-cloud images. "Tiny cloud" is cute shorthand for the edge nodes, the microservices, the unremarkable servers doing the unglamorous work of modern civilization. That is precisely where you place a long-term access mechanism if you want to position yourself at every gate before anyone knows gates exist.
Follow the Logs, Not the Leaders
The official advice is to check /var/log/messages for "successful password logins to accounts with no password." A tidy instruction—and a deliberate one. It turns your attention toward auditing the aftermath, while the deeper question is never asked: who authorized the bypass in the first place? The patched versions—3.21.10, 3.22.8, 3.23.8, 3.24.4—arrive just in time to suggest the whole thing was a routine hole being sealed. But a hole that large, that systematically threaded through every current release, does not get closed by coincidence. It gets closed because the access window has served its purpose, because the tools have been rotated, or because someone forgot to read the memo about which levers to leave visible. The logs you can check will never show the session that landed before you knew to look. So don't stare at the messages. Stare at the fact that this flaw existed in every version from 3.18.11 to 3.24.3—and ask why the public was only told after the fix was ready. Who was knocking during all those months? And what did they carry out in their oversized keychain?