OpenSSH 10.6p2 has been released with a workaround for a critical vulnerability
A newly released OpenSSH 10.6p2 includes a critical workaround for a vulnerability that affects Linux systems built with musl libc, with password authentication enabled and PAM disabled—configurations common on Alpine-based and some embedded or containerized systems. Due to musl’s non‑standard `crypt()` behavior, such setups can accept any long password for certain accounts, effectively allowing trivial remote login over SSH. Commenters focus on immediate mitigations (notably disabling password authentication), the likely impact on Alpine/Docker users, responsibility between OpenSSH and musl, and what this incident says about C-era APIs, error handling, and disclosure practices in an age of rapid AI‑driven bug rediscovery.
Vulnerability & root cause
- New OpenSSH release adds a workaround for a critical auth bug that only shows up on Linux with musl libc and PAM disabled.
- Bug centers on musl’s
crypt()behavior: for over‑long passwords it returns sentinel strings like*/!instead ofNULL, deviating from POSIX. - OpenSSH deliberately mixes password hashes to avoid timing leaks; combined with musl’s sentinel choice, this can cause accounts that should reject passwords to accept any long password.
- Some argue this is primarily a musl bug; others note OpenSSH’s “hash mixing” design contributes to the failure mode.
Affected systems & scope
- Conditions must all hold: OpenSSH linked to musl, PAM off, password auth on, at least one
*/!-style disabled account, and at least one real$5$or$6$password hash. - Alpine Linux (widely used in containers) is a major concern; musl-based OpenWrt/openwrt-like systems may or may not be affected depending on whether they use OpenSSH vs Dropbear.
- Dropbear is reported as unaffected in linked material; OpenBSD, glibc-based Linux, and PAM-using setups are also described as safe.
- Some posters think impact is overhyped due to many qualifiers; others note these conditions align with “recommended” hardening patterns, so real exposure may be significant.
Mitigations & SSH configuration
- Immediate mitigation:
PasswordAuthentication noinsshd_config; some point out keyboard-interactive/PAM can still allow passwords if left enabled. - Suggestions: use only public key auth or
AuthenticationMethods publickey/ certificates; put SSH behind WireGuard or similar; rely on console/BMC/VM access for break‑glass. - Counterpoint: password-less SSH everywhere complicates account recovery, especially after device loss or disasters.
musl, Alpine, and libc design
- Musl’s non‑POSIX
crypt()behavior and choice of*as an in‑band error sentinel are heavily criticized as “terrible decisions.” - Others stress that bugs happen everywhere and a single incident shouldn’t be used as blanket evidence Alpine/musl are uniquely insecure.
- Some note that musl documented its behavior and that ecosystem code not checking for it properly shares blame.
Languages, error handling & C
- Big subthread debates whether languages like Rust would have prevented this:
- One side:
Result<T,E>/Optionand culture around explicit error handling make sentinel‑based bugs less likely. - Other side: this is a logic bug, not memory safety; Rust or any language could still encode a bad sentinel or misdesign an API.
- One side:
- Broader lament about continued reliance on C for critical infrastructure; pushback notes POSIX, legacy, and practicality.
- Discussion extends to checked exceptions,
errno, and how poor error‑handling primitives in C encourage ad‑hoc patterns like sentinel strings.
Disclosure, embargoes & AI
- OpenSSH maintainers reportedly learned of the issue very recently and pushed a fast release.
- They argue long security embargoes are dangerous now that AI tools can rapidly rediscover bugs, implying rapid public fixes are safer.
- Several participants expect shorter embargoes to become the norm, with on‑call teams patching quickly even at inconvenient times.
Containers & embedded impact
- Concern that Alpine’s popularity as a Docker base magnifies risk, even if “proper” containers don’t run sshd.
- Others downplay this, saying most containers don’t expose SSH and often don’t have OpenSSH installed at all.
- For embedded and router environments, effect depends on whether they use musl‑linked OpenSSH vs Dropbear and whether password auth is enabled.