We are experiencing an infrastructure outage in one of our data centers. The issue is affecting multiple services, including our websites.
The Ubuntu archive is not affected by this outage. Our team is currently investigating and will provide updates in our public status page: https://t.co/8jhAZgWidZ
We apologize for the disruption and appreciate your patience.
https://t.co/TT92PdVdXw
By now you have probably heard about the sshhole bug. I didn't want to talk about on X until it had already attracted enough notice here that my analysis wouldn't be revealing anything to potential bad guys.
It's really, really bad for Alpine Linux systems and others using MUSL as their C library. However, I think we've dodged the bullet that was the worst possible case: it could have opened a gaping root-access hole in any router running OpenWRT. That's, like, maybe 30% of them? On the order of 100-500M units worldwide.
These are not yet confirmed findings, because frickin' chatGPT doesn't consider me authorized to do security analysis using it. I'm posting this hoping a real infosec guy with those creds can confirm.
I first learned of this bug this morning when @dfranke texted me "Anyone with an OpenWRT router needs to unplug it. Now. Run."
On further investigation, though, the bug only seems to bite if you have a root account that has shell access and a password field of "*" (disabled).
Out of the box, OpenWRT ships with an empty root password. This is not the same as a "*" password field and should prevent the MUSL bug from biting. And while it's quite common to disable password access to that account, usually people do that with SSH server-side configuration rather than by modifying the password file in the dangerous way.
All the other avccounts OpenWRT configures in have a shell entry "/bin/false", So you can exercise this bug on the ones with password field "*", but you can't exploit it.
So unless you've done something rather weird to its configuration, your OpenWRT based router is probably okay. You should, however, inspect it to make sure that your root account has a password ("x" entry in the hash field) and all the accounts that don't have shell access safely directed to /bin/false.
But again, this is not a confirmed result. If you're an infosec guy with the right tools, please check it immediately.
Cisco gives 27-year-old engineer unlimited AI tokens to rewrite 98% of the company's legacy code in 24 months — president plucks former startup founder, telling him to 'go nuts' https://t.co/7XSk2flVu6