237
Check if you need to update all your stuff - again. (sshhole.com)
submitted 1 day ago* (last edited 1 day ago) by to c/selfhosted@lemmy.world
89 comments fedilink hide all child comments
 

are you affected?

  • is your sshd running on musl? (alpine, openwrt, buildroot, yocto)
  • is it not using pam? alpine's openssh-server doesn't by default, or maybe you set UsePAM no
  • are password logins still on? they are by default
  • is there an account with just * as its password? key-only users, ldap users, root on alpine
  • and some other account with a real password?
  • then that * account takes any password between 257 and 1024 characters

on alpine's official aws and azure images that's the default alpine user, and it has passwordless doas. so it's root

on debian, ubuntu, fedora or anything else with glibc? going through pam? dropbear? openbsd? you're fine

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 1 day ago* (1 child)

Bottom of the page says what to do and gives 2 options to mitigate:

# update. openssh 10.6p2 fixes it.
$ apk upgrade openssh

# can't update yet? turn password logins off.
$ echo "PasswordAuthentication no" > /etc/ssh/sshd_config.d/00-no-passwords.conf
$ rc-service sshd restart

So if you disable password auth and only allow key auth, then you are unaffected (safe).

The introis a bit confusing but it means that if you have password auth on - then even if your regular ssh login requires a key, you are not safe.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •