News for hackers. Stuff that matters.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by solyin on Friday November 20, 2026 @12:35AM (#50570556)
At the end of the day, sysadmins care about "how fucked am I" from an email subject line. A replacement system would be "let me run a daemon on your network telling me what you run" with vendors telling me about the vulnerabilies and I'll tell you if you (the sysadmin) give a shit. Technically that's trivial, but who's gonna trust me to run a daemon like that on their network. Maybe you'd have luck with your public history, but that seems like quite the uphill battle.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by JJJollyjim on Friday November 20, 2026 @02:49AM (#50571453)
There are several products like that (Tenable comes to mind). Having used them, I would disagree that "telling you how fucked you are" is straightforward, because they all do a terrible job!

They will statically determine (e.g. by SSHing in and rummaging around) that a library with a known vulnerability exists on the filesystem, but determining the reachability of that bug in the system as a whole (can this be exploited by the entire internet, or 3 sysadmins, or no one at all?) is not really an automatable task.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by fc417fc802 on Friday November 20, 2026 @03:10AM (#50571609)
What if we standardized some sort of representation of known vulnerable combinations instead of a numeric score? As well as a standardized way to record system state regarding which libraries are used together and which of the resultant application stacks have network access or whatever else. That sort of data could be readily analyzed by automated tooling.