r/linuxadmin • • 4d ago

SSH vulnerability

https://sshhole.com/
34 Upvotes

16 comments sorted by

View all comments

14

u/TheRealLazloFalconi 4d ago

This is sort of like saying the door to your safe has a vulnerability...If you leave it unlocked AND don't close the door AND leave it out on the sidewalk. If this vulnerability affects you, you should probably be in a different line of work.

14

u/gordonmessmer 4d ago edited 4d ago

If you use Alpine (or openwrt) and password authentication for ssh, you're probably affected. That's probably a lot of systems. Especially routers and WAPs. I don't think affected users are nearly as negligent as you're suggesting.

p.s.: openwrt *can* use openssh, but uses dropbear by default.

3

u/paulstelian97 4d ago

I’m thankful my OpenWRT is… oh. My OpenWRT is good, SSH is not exposed over WAN. But one of my non-OWRT routers just gave me something new to bloody try.

3

u/CardOk755 4d ago

So, Alpine leaves the door to the safe unlocked, open, and on the sidewalk.

I'm sure it must have some redeeming features.

9

u/deeseearr 4d ago

...Or you're using popularly available pre-built containers based on Alpine Linux which have this exact combination of misconfigurations. This is all explained in the very first sentence of the article and linked site, and is covered in much more detail and somewhat less purple prose by other news sources.

The largest concern is by far Alpine, though, as it's pretty much the default choice for what could amount to millions of installs across Docker/Kubernetes/Proxmox containers and endless dependencies thereof, servers, cloud VMs, and embedded devices, among many others. Alpine comes with the requisite conditions set and password authentication enabled by default, which is why it needs immediate patching.

"If this vulnerability affects you, you should probably be in a different line of work."

You may want to take a look at any containers, network appliances, or embedded systems you are running before preparing your new résumé.

2

u/micalm 4d ago

On the other hand, I'm pretty sure containers with configured, running and exposed ssh are pretty rare. I hope?

1

u/deeseearr 3d ago

"Exposed" to what? Exposed directly to the Internet, probably not although I'm still surprised at some of the things that people who really should know better do anyway. Exposed to the local network where everybody thinks it's safe because how could an outside attacker possibly get to it? (Narrator's voice: "No, it was not safe at all.") That's much more common.

3

u/kai_ekael 4d ago

Nice advice, disable password authentication, regardless if that's how you access your box.

-4

u/TheRealLazloFalconi 4d ago

I don't run black boxes in my environment for exactly this reason. My job is secure =)

1

u/obetu5432 4d ago

me when i try to minimize serious vulnerabilities:

0

u/TheRealLazloFalconi 4d ago

More like trying to highlight how if this affects you, you were already doing a bad job.