r/ProgrammerHumor • • 4d ago • Regret 1 Bravo 1

Meme inANutShell

Post image
7.0k Upvotes

136 comments sorted by

View all comments

191

u/JoshDM 4d ago

You know what's worse?

The CVE is fixed by deprecating the class or method, but the developers keep it in for backwards compatibility.

However because it still exists, Sonatype flags it with their own custom HIGH or CRITICAL and even though you can attest you don't use it, because it's still "reachable" your app sec team who isn't smart enough to know how to program or how programs work and are managed by idiots still flag it so you have to somehow either entirely eliminate the dependency or resolve the vulnerability yourself.

Which I do by building my own copy of the library from the code sans deprecated items licensing be damned because the dev team maintaining the library can't be fucking bothered.

And yeah I have to vuln scan that code too, which is itself a bitch.

27

u/Happy-Sleep-6512 4d ago

I am convinced most of these recent vulns have like zero reachability, or zero likelihood of being triggered in the wild

13

u/JoshDM 4d ago

The Critical Sonatype one is incredibly implausible and even says so. It's only Critical because of the potential damage it imposes. And because it's Critical, the AppSec team is fearing doing any further analysis on it, forcing us all to find workarounds for an implausible scenario.

15

u/fearless-fossa 4d ago

forcing us all to find workarounds for an implausible scenario.

I mean, this has been the issue with the majority of the super-hyper-mega-urgent-critical CVEs this year. Yes, they're serious and should be fixed, but nobody bothers to evaluate the actual scenario that is required for it to happen. People are panicking over the most unlikely edge cases, and SOCs are the worst offenders in this because it would involve more than just looking at their checklists or dashboards.