The Morning Dev

Only the news worth knowing

‹
 
  • AAPL 344.17 ▼ 1.53%
  • MSFT 535.93 ▼ 3.58%
  • NVDA 181.60 ▼ 9.26%
  • GOOGL 282.57 ▼ 2.20%
  • AMZN 260.21 ▼ 2.19%
  • META 605.08 ▼ 3.96%
  • TSLA 343.69 ▼ 10.77%
  • AVGO 291.53 ▼ 10.43%
  • TSM 353.10 ▼ 10.78%
  • ORCL 115.16 ▼ 6.93%
  • AMD 404.40 ▼ 17.26%
  • NFLX 65.56 ▼ 1.25%
  • CRM 222.41 ▼ 2.07%
  • ADBE 246.44 ▼ 0.82%
  • INTC 52.25 ▼ 10.33%
  • IBM 247.11 ▼ 2.84%
  • PLTR 154.99 ▼ 9.73%
  • SNOW 269.54 ▼ 7.25%
  • NET 244.51 ▼ 8.28%
  • SAP 243.53 ▲ 1.45%
A69/100

Vulnerability · critical

OpenSSH authentication flaw on musl/Alpine systems without PAM, with 10.6p2 workaround

Tier A · Patch today – Before you go home

Who’s exposed: Alpine and musl systems running openssh-server without PAM

Tier A because: Core infrastructure or popular tool AND remote, no login AND full takeover

Reach

Attack

Damage

Fix

Core infrastructure · Popular tool · Remote, no login · Full takeover

The Brief

  • OpenSSH 10.6p2 was released with a workaround for a critical flaw affecting Linux systems that use musl libc with PAM disabled, such as Alpine Linux.
  • Dubbed "*sshole", the flaw lets attackers log into accounts configured to block password authentication by sending an oversized password.
  • Attackers need network access to the SSH server, an account name, and a password between 257 and 1,024 bytes long.

Why it matters

Servers on affected musl systems without PAM can be accessed through accounts that were meant to be key-only, so exposed SSH servers and Alpine-based containers need updating or hardening now.

The checklist behind the tier

Checklist · 5 of 10 yes
YesHits tech teamsJudgment: OpenSSH servers on Alpine are run by ops and IT teams, so this affects systems they operate.
YesCore infrastructureJudgment: OpenSSH is core infrastructure that nearly every team runs for remote access.
YesPopular toolJudgment: OpenSSH is a widely used, mainstream server package.
NoExploited in the wildNo source reports observed attacks using this flaw; sources only describe that it allows login.
NoPublic exploitNo source says exploit code or a step-by-step PoC is published; details are not described as public.
YesRemote, no loginThe Hacker News: attackers need only network access, an account name, and an oversized password, no valid credentials.
YesFull takeoverArs Technica: the vulnerability lets hackers log into devices with no password, an authentication bypass.
NoSecrets exposedNo source reports stolen credentials, keys, configs, source code or customer data.
NoSupply chainNo source reports compromised packages, updates, build pipelines or signing keys; it is a normal bug.
NoNo fix yetThe Hacker News: OpenSSH issues emergency fix; LWN: version 10.6p2 released with a workaround.

Timeline

  1. Alpine Linux security advisory published

  2. OpenSSH 10.6p2 released with workaround for the musl/PAM flaw

  3. Hacker News: Front Page

    OpenSSH 10.6p2 has been released with a workaround for a critical vulnerability

  4. Hacker News

    170 points · 81 comments

  5. LWN.net

    Critical security vulnerability affects OpenSSH on Alpine Linux systems

  6. Hacker News: Front Page

    OpenSSH 10.6p2 Critical workaround for alpine without PAM

  7. Hacker News

    131 points · 7 comments

  8. Hacker News: Front Page

    Alpine Linux Security advisory: OpenSSH-server password authentication bypass

  9. Hacker News

    539 points · 105 comments

  10. The Hacker News

    OpenSSH Issues Emergency Fix for Flaw Letting Long Passwords Bypass SSH Auth on Alpine Linux

  11. BleepingComputer

    OpenSSH flaw lets attackers log into password-disabled Linux accounts

  12. Biz & IT - Ars Technica

    Meet *sshole, the vulnerability that lets hackers SSH into Linux devices

Full coverage · 7 sources

What developers are saying

Based on 193 comments · Mixed reactions

Commenters treat the flaw as a serious problem rooted in musl's crypt() behaviour and praise the fast release, though some argue it reflects broader problems with C code and Alpine. Others say their own setups were unaffected, and some question whether the default Alpine install is vulnerable at all.

  • musl crypt() design flaw25%
  • Praise for fast disclosure15%
  • Whether Alpine defaults are affected15%
  • Disable password authentication advice20%
  • Criticism of C and distro choices25%

In favour

  • + Fast release is justified by rapid rediscovery of bugs by AI agents and the risk of long embargoes
  • + Disabling password authentication is a sound general hardening step

Concerns

  • − musl's crypt() returning '*' as an error indicator is seen as an unsafe API choice
  • − The default Alpine install may not be affected because it uses '!' as the shadow placeholder
  • − A workaround rather than a fix raises questions
  • − Following the advice blindly could lock administrators out of machines
  • − Docker containers are often slow to update their base images

“The musl code in question is nuts. The API it implements is awful.”

amluto on Hacker News

“i think it's just unbelievable there isn't a bigger push to move away from c to languages that can prevent stuff like this from happening.”

slopinthebag on Hacker News

“By blindly (or agenticly) following those instructions the risk is getting locked out of some machine.”

alanfranz on Hacker News

First seen · 7 sources · 193 comments · Full story page · How tiers are decided