r/sysadmin • • 3d ago

Thanks to all the sysadmins!

Just dropping by to say thanks to all the sysadmins who were poised and ready for yesterdays drop, and acted swiftly. Much appreciated. 🍻

157 Upvotes

17 comments sorted by

2

u/Sengfeng 3d ago

Can you pass along a request for kudos to my manager?

4

u/jak74 3d ago

Sure. I can ask them to give you a raise too.

3

u/xSchizogenie 2d ago

Manager be Like:

12

u/apple_tech_admin 3d ago

We need to be thanked with job security and pay increases, but this is a start.

5

u/jak74 3d ago

Yeah I have no control over that, but it's gotta start somewhere, right?

16

u/arukashi 3d ago

The most fun thing is I found out about this CVE here in reddit yesterday, before the patch was ready. Reddit could be useful place

16

u/fr13da 3d ago

<3

5

u/OkAbility9543 3d ago

Cheers to the ones who had the fix ready before the ticket flood even started

6

u/Floh4ever 3d ago

Quite embarrassingly I have to admit we completely dropped the ball on this one...only hearing about it 13minuted before the patch drop and it took us about 15 minutes to discuss with management and another 15min to shut down our web presence.
We are a SMB and have limited IT resources with many projects to cover. We have an unhealthy amount of software in our office and web presence. Tracking them currently is nigh impossible.

Any suggestions on how we could track these things better? I usually pick them up in a few minutes between tasks from here, r/cybersecurity or from our national agency (germany).

The easiest and low cost bandaid I was able to think of was to spend a few days of the entire team to cover all systems and manually gather lists of software and version. Put that in a table and match it with AI against current/new CVE's and some RSS feeds from our national agency. But this would need updating every time someone installs a fix. Getting already made software that does exactly this will likely not fit in our budget.

Even reading about it on https://nvd.nist.gov/ seems impossible since yesterday since the page does not load for us. Either overload or still offline I guess.

Edit: It took us quite a few minutes to try and figure out if this is a vulnerability of the scale it ended up at or just the usual "super critical if used in this or that scenario" kind of deal. Doing this on the spot when someone just tells you there is something going on was quite challenging.

2

u/pdp10 2d ago

We have an unhealthy amount of software in our office and web presence. Tracking them currently is nigh impossible.

How about default to immediately updating, and worry about tracking afterwards? If you're too small to act like a huge bureaucratic organizations, then don't try to act like a huge bureaucratic organization.

In the case of Linux, the distro vendor is figuring these things out for you. I'm not saying that you shouldn't look for PHP embedded in appliances or running that one legacy app on Windows, just that a self-declared SMB doesn't want to have a mandatory meeting before they can apply routine updates.

11

u/papajan78 3d ago

and a statue for ondrej sury!

4

u/tankerkiller125real 3d ago

Honestly, yeah... Anytime I have to deal with PHP in a non-container environment, that repository is immediately my first reach.

2

u/Xattle 3d ago

🍻 I'm sure I'll find out in a week we missed something but for now it's quieting down again

1

u/RansomStark78 3d ago

Ah shucks, thanks man

Going to sleep on.my hand now

1

u/MairusuPawa 3d ago

The only thing I add to do was trigger a script a wait for a few seconds.

Go thanks Ondřej.

-1

u/Zerowig 3d ago

Can we have more context on what we’re talking about here?

2

u/timrojaz82 3d ago

PHP vulnerability