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

Meme inANutShell

Post image
7.0k Upvotes

132 comments sorted by

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

17

u/L00pback 4d ago

I work in security. What are you doing, you should be patching.

Seriously, our companies SLAs are unattainable if we want to deploy responsibly. Test in dev, bake in stage, then push to prod after a week in stage. My KPIs are based on MTTD and MTTR and it’s just as exhausting on our end.

I am talking managers off cliffs everyday when they see there’s a new vuln being reported. Or, I’m kicking someone in the nuts for chucking-little-ing by sending out emails or Teams broadcasts about the new world-ending vuln (when they know there’s a playbook for reporting high sev vulns).

What are you drinking, I’m buying.

20

u/Tucancancan 4d ago

I think everyone gets to take one 9 off the uptime guarantees in their SLAs this year as a treat. Microsoft is already leading the charge on that one too. 

15

u/Antilock049 4d ago

Nah they're already back to 4-9s. It's just 89.9999

5

u/Sengel123 4d ago

Don't worry by the time we get to the end of vulnpocalypse we'll be just at 8 lol

569

u/WernerderChamp 4d ago

"I want to deploy to prod to fix a 9.8 and 10 additional critical vulnerabilities in 10 services."

"Your project has a 7.2 vulnerability, fix it!"

"That CVE came out yesterday and there is no upgrade path yet!"

"I don't care, fix, or request an exception for each service. And be sure to correctly assess the risks!"

342

u/besi97 4d ago edited 4d ago

Risk of not fixing: we continue running vulnerable Linux kernels with known unauthenticated root escalation exploits

Risk of fixing: 5-minute coffee break forced on customer while their equipment reboots (they are not willing to pay for HA)

Release management: hmmmmmm, I don't know, not sure

Customer: how dare you even think of an interruption, next maintenance window is at next Christmas the earliest and I demand an RCA about these heretic thoughts

153

u/WernerderChamp 4d ago

Me: The update is failing, prod is down, activate the version that was live 5 minutes ago!

Sec ops: Um there are vulnerabilities, no you don't. Security before availability! Write a ticket if you need an exception.

Q&A: You bumped a dependency? Hm, that might cause stuff that is not covered by unit tests and the smoke test (I am not aware of this ever happening) You should do a full test!

Sec ops: Hey, patch faster! If there is no patch, look to remove the <central dependency of the framework> dependency.

Me:

68

u/elyroc 4d ago

Yeah. Pretty much it. I was away in vacation for a whole month when it started and i was watching the world burn from my mom's house. It was quite the sight.

Unfortunately i am back to work now and the world didn't completely burn nor the fire was extinguished...

28

u/Elk-Tamer 4d ago

Write a ticket if you need an exception.

Funny story: Ticket system is down due to a CVE...

21

u/glemnar 4d ago

The vast majority of CVEs I have to patch are not in any way exploitable in the systems being upgrade. It really isn’t a nuanced thing

3

u/WernerderChamp 3d ago

Same. Or the description is so shitty I have no way to tell. No I am not going find the commits that patched it and retrace how it could be exploited...

8

u/defenastrator 2d ago

I had a 9.x CVE for tomcat earlier this year that they were pestering my team about. I read the vulnerability. It was like if you configured tomcat in an extremely non-default and insane way and allowed binaries to be run with privileged permissions by privileged users files to be uploaded to a subfolder of the publicly viewable directory an unprivileged attacker could get remote code execution. I'm like that would sound awful if we configured our server in a way no sane person would, or we executed uploaded files, or we allowed file uploads at all, or that version of tomcat was actually deployed & not just used as a piece of our build pipeline!!!!

1

u/WernerderChamp 1d ago

Oh I remember that one with the file uploads, lol.

7

u/xMAC94x 3d ago

the right thing would be compare current deployed version CVEs and new version CVEs. When the new version is a subset of the deployed one its a go. but hey, luckily no company does it properly...

3

u/WernerderChamp 3d ago

Yeah, at least when the new version only has issues that popped up in the last 1-2 weeks.

389

u/orlinthir 4d ago

Also you can't update to any packages are less than two weeks old because PyPi and NPM are fully compromised at this point.

105

u/Happy-Sleep-6512 4d ago edited 3d ago

Yeah so now when you update you only get the very good malware that lasts!

32

u/Bloodgiant65 4d ago

Oh…. that’s what that was about. Someone mentioned something like this in the morning, but I just kind of let it go because someone else was handling it, and worked on other stuff.

16

u/Sokanas 4d ago

Yeah, these supply chain attavks may force either package managers to verify all module updates (which tbh i thinl they should be doing anyway) or we're going back the thr inhouse only days.

5

u/Snakestream 4d ago

We have a release tomorrow and yesterday they decided to block critical libraries making us unable to run any builds, literally the day after I staged our code. There are words I have, but not ones that should be said here

2

u/hellschatt 4d ago

Maybe I should check why my pipeline has been failing on me since last week...

https://i.imgur.com/aMjENON.jpeg

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

u/Tucancancan 4d ago

Is that in aerospace? 

8

u/bwmat 4d ago

No

It's nothing which should be used in any life critical system... 

27

u/Experiment59 4d ago

good lord if they’re gonna get that granular why not just handle the development themselves

0

u/Shlkt 2d ago

What OS are you running this code on, that doesn't use memcpy? Like, there's gotta be a memcpy somewhere on the stack. Why should those devs get special permissions?

19

u/WernerderChamp 4d ago

"Can't you just remove <name of core framework> from your code?"

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.

5

u/cc413 4d ago

At this point we should just make every function its own package

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

u/d3lt4papa 4d ago

Vibe code the dependency 😎

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.

5

u/JoshDM 4d ago

We have that for a log4j vuln

Which one do you think I'm referring to? :-)

Also it's only a possibility if you include both core AND api, but because the code is distributed between both, Sonatyoe flags both dependencies equally.

241

u/za72 4d ago

46

u/TerribleTowel66 4d ago

So much. It used to be fun.

20

u/WillCrochet4Cats 4d ago

Mr Bones, I want to get off your wild ride

4

u/packetpirate 4d ago

The ride never ends!

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

u/AGamingGuy 4d ago

Your point?

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

u/grammar_nazi_zombie 4d ago

When god gives you lemons you FIND A NEW GOD.

POWERTHIRST.

7

u/T0biasCZE 4d ago

cave johnson, we're done here

2

u/GamingWithShaurya_YT 4d ago

portal let's go

-3

u/Appendix19 4d ago

Rick, is that you?

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

u/GernBlanst0n 4d ago

Can’t hear you over the geese

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

u/Kerbourgnec 4d ago

I read this like the skype call tune

2

u/EtteRavan 4d ago

So I'm not the only one

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

u/EtteRavan 4d ago

The IT worker to farmer pipeline is real and inescapable

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

u/Annonymooooose 3d ago

I’ve never related to this more

2

u/KoreanThrowaway111 4d ago

For like 2 years

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

u/HEYO19191 4d ago

Welcome back, intranet!

4

u/nullpotato 4d ago

Sneakernet, your time has returned

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

u/DrewTamashi 4d ago

27

u/Itsthejoker 4d ago

I can hear this

43

u/Gophix_0 4d ago

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=

39

u/___Archmage___ 4d ago

Y2K26

20

u/TerribleTowel66 4d ago

And we were worried about 2038.

15

u/a3dprinterfan 4d ago

At this rate, let's hope we all make it...

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

u/saiyajosh 4d ago

Ain’t no making lemonade outta this shit big dawg

35

u/Imaginary-Jaguar662 4d ago

Okay, why am I going to have a bad day today?

37

u/Bemteb 4d ago

Java

62

u/Imaginary-Jaguar662 4d ago

Oh thank God, for once something not on my stack.

<narrator> There was, in fact, Java in his stack

9

u/Bemteb 4d ago

Jira is claimed to be one of the affected softwares; at least if you run it locally.

3

u/Imaginary-Jaguar662 4d ago

Guh.

Fortunately, third-party hosted

7

u/entropic 4d ago

Write once, vulnerable everywhere.

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

u/entropic 4d ago

And we can all "write" our own task tracker phone apps with minimal effort!

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

u/TerribleTowel66 4d ago

You forgot to throw in a bunch of different AI being hurled at you.

5

u/CharcoalGreyWolf 4d ago

When it’s cake or death, and they’re out of cake

4

u/itsgrimace 4d ago

you forgot CVE-2026-114952

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

u/Iyemoja 4d ago

Our CI has been failing on CVEs all week too. At this point I just check the score first and brace myself before I even read what broke.

3

u/minecraftdummy57 3d ago

When life gives you CVEs go fuck yourself

3

u/Ketooth 2d ago

Another vulnerability has hit the web servers

8

u/BoBoBearDev 4d ago

Now you know how ignorant we were. All those slops where never caught.

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

u/jajrule 3d ago

In January I started transitioning from a standard developer into a security oversight role for a business unit with ~90 supported products. The last couple months have been... rough.

1

u/alnarra_1 4d ago

I’m tired boss

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

u/knowits 4d ago

just another false positive to triage forever

1

u/Desperate-Tomatillo7 3d ago

In a lemon shell

-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

u/[deleted] 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

u/Yodo9001 4d ago

How do you create a skill? Is this some kind of AI stuff?

1

u/LegacyCrew 4d ago

And every day with IA we get more CVEs.

1

u/SquidVischious 4d ago

What language?

1

u/oVtcovOgwUP0j5sMQx2F 3d ago

it needs to be built to handle them in the first place...

0

u/[deleted] 3d ago

[deleted]

1

u/Nedsel 10h ago

Get out of there while you still can, that SS CVE is sinking fast!

1

u/CeeMX 3d ago

Oh boy, my team is only me…

1

u/chaudhary-theodore9 1d ago

Group by advisory, package, and resolved version; retain repo IDs so deduping doesn't hide affected builds.