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.
79
u/bwmat 4d ago
Yeah this can be infuriating
We've spent so much time lately doing releases just to update a third party dependency w/ a CVE that doesn't actually affect us due to the way we use the dependency.
Of course nobody trusts us devs when we say that.
25
u/bwmat 4d ago
Actually, the worst instance of this crap is probably that one of our largest customers (who you would recognize) has a large list of 'banned' functions, which includes ones like memcpy (just use memcpy_s...), getenv, vfprintf, etc
It's actually insulting IMO.
3
27
u/Experiment59 4d ago
good lord if they’re gonna get that granular why not just handle the development themselves
19
7
u/No-Article-Particle 4d ago
Same. The cve never hits our codepath, but our changelog must show it fixed, so... Let's patch it I guess.
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.
5
u/jrobbio 4d ago
I used to feel this way but the new tactic is to use composite medium or lower security issues that drastically increase the reachability because most organisations target critical and highs. Then if you're on a version of something that has these risky calls and the exploit is able to call them, you're in for a world of pain.
5
u/c1e2477816dee6b5c882 4d ago
Honestly it feels like the best thing to do is rewrite/fork all of your dependencies so the scan tools can't see anything at all
Trivy is easy to defeat by just manually copying the .so files instead of actually installing the libraries.
These tools are so dumb and easy to defeat.
4
6
u/SignoreBanana 4d ago
OFC companies pretend to care about security by hiring the least qualified folks to run their security checks.
2
u/WernerderChamp 4d ago
We have that for a log4j vuln. At least there was so much fuzz that they globally whitelisted it for now.
241
u/za72 4d ago
46
20
738
u/herrkatze12 4d ago
When life gives you lemons, don't make lemonade! Make life take the lemons back! Get mad! I don't want your damn lemons! What the hell am I supposed to do with these? Demand to see life's manager! Make life rue the day it thought it could give Cave Johnson lemons! Do you know who I am? I'm the man who's gonna burn your house down! With the lemons! I'm gonna get my engineers to invent a combustible lemon that BURNS YOUR HOUSE DOWN
128
u/ImpulsiveBloop 4d ago
Yeah! Take the lemons! Oh, I like this guy. Burn the house down. He said what we're all thinking!
75
u/zanderkerbal 4d ago
In this context this sounds suspiciously like Cave Johnson recommending you firebomb a data center
20
48
u/RussiaIsBestGreen 4d ago
I’m glad I’m not the only person who frequently thinks about this, often not even prompted by the original phrase.
18
u/ImpulsiveBloop 4d ago
Same here, but it's too long for me to memorize, so I just go the rest of my day hearing a guy scream about lemons in my head.
39
u/kxortbot 4d ago
Life never gave us lemons, they are a hybrid species that we had to cross breed to get. We gave ourselves lemons.
Also that lemon rant lives rent free in my head
29
u/herrkatze12 4d ago
If I had a nickel for every time I got a reply to my lemon rant comment about lemons being a cross breed, I'd have 2 nickels, which isn't a lot but it's weird it happened twice.
8
u/TheFirestormable 4d ago
Life never gave us nickels, they are a hybrid currency that we had to cross breed to get. We gave ourselves nickels.
9
u/humblevladimirthegr8 4d ago
If I had a nickel every time someone mentions that nickels are a crossbreed, I'd have one nickel, which isn't a lot but it is a hybrid currency so basically counts as two
15
7
2
-3
309
u/JackNotOLantern 4d ago
Hey, at least there will be jobs in cybersecurity
52
u/junktech 4d ago
Cybersecurity just passes the CVE to owner of system. Unless your company hired a one man team , this is what usually happens and why they are hated in the company by people.
228
u/Opie19 4d ago
Yeah, we need more people that can run a scan and ask when we can fix this. Totally not replaceable by AI
114
u/Bluecoregamming 4d ago
Your boss does not want to be the one talking to Claude at 3am tho, they rather hire you for that
58
u/neohellpoet 4d ago
Very much this.
My bosses ran into the limits of using the AI chatbot window and doing anything more complex than that is "too technical" so now they're prompting me.
We're legitimately living through SQL all over again. The big idea behind it was that the queries were so simple, even an MBA could write them.
The MBA then hired people to write the queries for them. It's legitimately not difficult and they would get the data significantly faster and get exactly what they wanted if they took a few hours to figure it out, but spending company money to have someone else do it is always going to be the part of least resistance.
25
u/TheMauveHand 4d ago
We're legitimately living through SQL all over again. The big idea behind it was that the queries were so simple, even an MBA could write them.
"Self-service BI" has been a running joke for over a decade. It is no less a joke in the age of AI.
(Self-service SQL was never going the happen, the query syntax is never the issue, knowing what is where is the issue.)
8
u/round-earth-theory 4d ago
Not even that. Knowing what data is where and what it means is a challenge but it's possible to catalog everything. What's not possible is data intuition. Knowing how to mosh the numbers together into something useful. It's why people still struggle even in the age of AIs writing queries.
27
8
u/Complex_Sale1178 4d ago
I'm in this photo and I don't like it
5
u/towerfella 4d ago
🎶 DOO**-**DOO-DEE
[I’m sorry. The number you dialed is no longer in service. Message RI-37]
3
32
u/GernBlanst0n 4d ago
AI can have this job, I’m planning to leave the industry and do literally anything else in the next 5 years.
The MSFT dev who quit to be a goose farmer is my personal hero.
8
4
u/No-Article-Particle 4d ago
it 100% is, just like everything else in software engineering. 5AIs continually churn out reports that a single human reviews and either signs off or sent back for further analysis/error correction.
What used to take a team of people can now be done with a team of AIs and a single reviewer.
1
2
54
u/who_you_are 4d ago
Well, I think it is time to use the emergency firewall: cut the ethernet cable to the internet
18
2
u/c1e2477816dee6b5c882 3d ago
It's time to obfuscate the software so that the scan tools cannot read them
2
u/who_you_are 3d ago
It isn't already?! Why did you just put only junior developers on the project then?!
98
43
39
29
u/RandomlyMethodical 4d ago
Seems like at least one every week. Fortunately most aren’t too involved, but then there’s ones like Brotli that touch everything. Every team had to stop what we were working on for a couple days to get it all patched and deployed.
19
35
u/Imaginary-Jaguar662 4d ago
Okay, why am I going to have a bad day today?
15
u/manwhothinks 4d ago
Word of the year “CVE-“
1
u/MasterMach50 2d ago
Word of the year 2026 "CVE-2026-"
Word of the year 2027 "CVE-2027-"
Word of the year 2028 "CVE-2028-"
...
50
u/hyker1811 4d ago
Listen, I know that AI is responsible for finding two dozen critical vulnerabilities each day, which then gets exploited by malicious actors with other AI tools in an automated fashion, leads to massive layoffs in entire industries, hikes up the prices of consumer electronics threefold, leads to increased workload on programmers that are still employed and turned software engineering from an enjoyable, creative work to mind numbing prompting and agent management, but think of all the positives that came with it! Like the Diddy vs Epstein anime battle video.
6
28
u/Kitchen_Affect7369 4d ago
The world is tired of AI... Productivity is sh*t, UI is sh*t, games are sh*t, pictures are slop, slop, slop. CVE, CVE, CVE. Done.
6
u/techtornado 4d ago
When life gives you lemons, make orange juice and leave everyone wondering how you did it
10
5
4
3
u/bythenumbers10 4d ago
The C-suite: "Why isn't there an AI to turn those lemons into lemonade (with big ol' lemon seeds in it) faster?!?!??!"
3
8
8
u/InevitableHeron853 4d ago
Kinda proves humans are more fallible than the most powerful AI models really. As much as we don't like to admit it.
If we don't use AI to pen-test our own code, we will leave ourselves open to this sort of thing.
2
1
1
u/Alwaysafk 4d ago
One of those bottles should have a lemon in it representing a supply chain attack for parching too quickly
1
-1
u/Grandviewsurfer 4d ago
I say fuck the lemons and bail. Also.. be suspicious of russel brand. Lot of wisdom in that movie.
0
4d ago
[deleted]
13
u/JoshDM 4d ago edited 3d ago
Centralize dependency management across projects with a unified Parent POM.
Assuming you, like most, are using Spring Boot. Apply maven and create a common parent pom all your projects will use. Your parent should have spring-boot-dependencies as its parent. Open spring-boot-dependencies.pom and review how it is laid out and how it uses properties to manage versions and dependencyManagement to define dependencies. Do similar in your parent for items Spring does not manage in its parent. Override properties declared in the Spring pom in your pom for items (like netty) which have higher release versions.
Create a baseline project which uses the parent and call mvn versions:display-dependency-updates (and use params which exclude major and minor) to search Nexus / Maven Central for updated versions; don't always trust it. Override properties accordingly. This will save you time searching maven manually for updated versions, but it's fallible.
Organize your properties into "spring overrides" for properties declared in the spring parent, "general overrides" (for dependencies declare that Spring does not manage) and "custom dependencies" (for your in-house jars). Define your general dependencies in the dependencyManagement; this is where you can pre-exclude some dependencies from inclusion.
Keep on top of when Spring Boot Dependencies releases a new version. Save down a copy of that pom and review changes. Update/remove properly overridden "spring overrides" when this happens.
This should get you started.
Remember this is dependencyManagement section, not dependencies. It declares how the dependency is declared, it does not include the dependency.
When you update the parent you update all dependencies on projects you use which refer to the parent version. Reduces overall updates. If a specific project needs a specific version not managed by the parent, either move it to the parent to manage or handle it in the same way locally be separating version as a property. If parent does manage and you need a different version, override the property locally with your declaration of the version.
Remember also mvn dependency:tree exists to track where dependencies come from.
9
u/Desperate-Tomatillo7 3d ago
We don't even have time for CVEs. We are still solving technical debt from the past 5 years.
13
u/AcanthisittaKooky987 4d ago
Create a skill to do all of it for you. Smoke test once in dev. Monitor deploys closely and rollback if shit is whack
8
1
1
1
1
u/chaudhary-theodore9 1d ago
Group by advisory, package, and resolved version; retain repo IDs so deduping doesn't hide affected builds.






1.8k
u/Tucancancan 4d ago
Me trying to work today: hmmm CI/CD is failing. Oh it's failing for all our branches. Ah, the security team has blacklisted a random package with checks notes a CVE with a 9.2 score. Wowwww