I've been setting UsePam = no for decades because leaving it on meant that it'd still present a password login of keys failed. Is this still the case, was I wrong from the beginning, or is this somehow ok?
post
This isn't nearly as bad as I thought it was. Also the author is very reliant on AI to the point where they didn't think about what if someone wipes the logs.
Any effected devices should be wiped and redeployed
Jesus Christ. Why?! How?
Edit: I can't figure out how to upload gifs to Lemmy... please imagine castle-nathan.gif
castle-nathan.gif
I don't know why, but I always assumed that image was from Firefly. It's the same color shirt and everything!
There are a lot of references to Firefly in Castle. It's quite entertaining.
Didn't he dress up as a "space cowboy" in one episode?
I can't figure out how to upload gifs to Lemmy...

The container thing is extremely unlikely. However, having worked with developers before, I know there are people who are running those AWS and Azure images with internet-facing SSH password authentication. If they hadn't already been hacked, they've all been hacked now. Somebody just had to check Shodan for hosts in those IP ranges running OpenSSH and try a few usernames.
did you get hacked? check.
$ grep "Accepted password" /var/log/messages
That's a really bad check unless you have an external box receiving logs and you're looking there, because the first thing that a sophisticated attacker is going to do if they get in as root is remove the signs of their presence.
I wouldn't recommend deploying any ssh server without reviewing the config and believe sane defaults are sane.
I'm no cybersecurity expert, but from what I've heard from those who are, this is the new normal as anyone who formerly had no chance due to being a "script kiddie" can now just prompt an AI* to eventually find a vulnerability.
* oversimplification redacted
You'd think that but so far I haven't seen an actual PoC exploit for the PHP vulnerability that doesn't require misconfiguring the server. And this is over a week after the patches were released.
Yep, those new fangled slop-kitties. The worst part is that there brute force hacking is being subsidized by people 401ks.
The irony - of course - is that their 401k money goes right into hacking those same people's 401ks.
... but at least we can brainrot an entire generation with glass fruit slices and put artists out of work?
Now if you'll excuse me, I have to go convince someone that the TikTok deepfakes they're watching aren't real and that cops don't really employ nanny-boo-boos to unsettle criminals during interrogations. No, I'm not joking.
It's not quite as simple as that. The author in this case followed a pretty specific trail to find the bug.
Where AI helped was as the last step. They already knew what the bug would do and where to look, but actually looking through the source code for all the possible musl implementations out there would have taken a lot of time.
So they brute-forced it instead and asked AI to spin up actual running instances of all those implementations and simply tried the bug against each of them, rather than looking at all the code.
The way it works is that finding vulnerabilities required a lot of technical understanding and mental effort. A software could have a glaring hole in it for years without anyone finding out simply due to nobody really looking. AI just gives you the ability to do rudimentary exploit analysis around the clock without having to spend your own time. This is a wake up call to anyone making software in sloppy fashion.
But it isn’t quite as easy as saying “AI hack into this service”, if the person doing the hacking is using the same model as the person who made the service, and that person already asked the AI to do that and fixed the resulting exploit prior to release.
Even projects that use AI in a limited fashion to code or even not at all, often use AI to at least do some red team stuff prior to release.
I don’t really foresee any way this doesn’t even out eventually.
I use alpine with an ssh port exposed to the internet so I can connect to it. This doesn't seem to be an issue if you configured your settings to be secure.
Never use just default settings.
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?
SSH enabled and the SSH port of the container accessible and it's set for password auth.
Maybe something like git forges and gist alternatives?
Linux phones? PostmarketOS is alpine-based. And a lot of people may ssh to their phone.
That website is atrocious. It's the web design equivalent of shoving five kilograms of sugar and whipped cream in a cup of coffee.
Now, now. Starbucks is a very successful business.
Yes, it was a stroke of genius to label their mediocre confectionery as "coffee", although it can lead to near fatalities when someone who's only ever had Starbucks encounters real coffee for the first time.
Still, my point stands. That website is like 20% useful content, 40% flair, and 40% wasted space.
"Cyber" ppl love to do this. This is basically their resume I guess? They have to sensationalize absolutely everything they can (not that this isn't an important bug, but this could have been a 1-2 page white paper imo (like many of them))
I'm assuming this is only if you allow password authentication? If you're only allowing certificate based auth you should be safe, right?
Correct, password authentication must be enabled on the SSH daemon side of things to be vulnerable. The user account being logged into, on the other hand, can't have a password set. But overall, PW auth must be on. The website OP linked is exceedingly bad at explaining the actual problem, see Alpine's announcement for better info.
https://alpinelinux.org/posts/2026-11-05-openssh-password-authentication-bypass/
OP I know you're trying to do good, but please try to understand the vulnerability before spreading FUD
Most containers don't run ssh right?
If I'm running containers on Alpine, doesn't that mean that they already don't offer SSH (sshd)? The entire point of Alpine as a base is to not add stuff you don't need.
Everything behind a good firewall and proxy.
No public facing url should ever not be proxied.
Only ports you explicitly forward. Ever.

top 50 comments