- cross-posted to:
- linux@lemmy.ml
- cross-posted to:
- linux@lemmy.ml
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
I mean, not that it’s not severe, but which container images have ssh baked in? If you’re using good stripped down images, you’re fine here.
Not sure where the overlap is between"ssh is enabled" and “one of those OSes”. LXCs maybe?
Even if there is ssh it probably is going to be dropbear and it is unlikely that password based authentication would be enabled
SSH enabled and the SSH port of the container accessible and it’s set for password auth.
Linux phones? PostmarketOS is alpine-based. And a lot of people may ssh to their phone.
Most Android apps that make a ssh server use dropbear afaik.
Maybe something like git forges and gist alternatives?
They use key based authentication
I wonder if Forgejo / Gitea instances are vulnerable
Good Point! I’ll check if my forgejo container has password auth enabled. :D It’s LAN only though.
Remember, password-auth off is the problematic setting.
No you’re wrong. Stop dramatizing and spreading false info. From your link:
Prerequisites: Are password logins still on?
You can’t trigger this if password auth is disabled.
Ah. Thanks for the correction. The intro + where I originally learned this from made me overreact a bit, it seems.