LinkedIn, please stop sensationalising yet another CVE. This time: #sshhole / #sshole
There's no need to sensationalise this. ALL of my feed is about SSHhole. I don't know a single systems administrator who has exposed SSH with password login, especially directly to root.
Most of you are not only overblowing the issue instead of reasonably reporting on it: yelling "️🚨⚠️⚠️️🚨 WARNING WARNING WARNING ️🚨⚠️⚠️️🚨" and further contributing to the system administrator burnout (which is a very serious issue, hell, every single minor vulnerability with minimal practical impact gets shoved down my throat from 30 sources every day -- how do you expect sysadmins to filter out all the garbage they get because of all of the cybersecurity slop, and deal with the issues that actually have huge impact), but also genuinely spreading disinformation by saying "enter 257 characters and BOOM: you have root"... this is simply not what this vulnerability is.
It's not a rootkit. It's not daemon -> root.
It's a user authentication bypass on systems that:
- Use MUSL libc
- Do not use PAM
- Run OpenSSH
- AND have password-based authentication on
It's not even an Alpine-specific issue, despite headlines blaming specifically Alpine.
It's a technically a serious issue. But it's not what most of you make it out to be (257 chars => root). And it's also not what most production systems will be affected by.
Worth updating, well worth fixing, but just... come on... let's stop floating within the illusion of catastrophe and get back on the ground of a second.
Stop the clout chasing via sensationalised CVEs and high CVSS score misinterpretation. I'm so sick of it. Every system administrator is. It's fatiguing. Every other day of the past couple of months has been nothing but this.
#cybersecurity #cve #burnout #cvss #sysadmin #sysadm #cybersec #devsecops #alpine #ssh #openssh #linux
— | post #799 | raw version