tofu@lemmy.nocturnal.garden to Selfhosted@lemmy.worldEnglish · 2 days agoJava4Shell, NGINX2Shell and more: Why we are not at "Yellow"isc.sans.eduexternal-linkmessage-square10linkfedilinkarrow-up175arrow-down11
arrow-up174arrow-down1external-linkJava4Shell, NGINX2Shell and more: Why we are not at "Yellow"isc.sans.edutofu@lemmy.nocturnal.garden to Selfhosted@lemmy.worldEnglish · 2 days agomessage-square10linkfedilink
minus-squareryannathans@aussie.zonelinkfedilinkEnglisharrow-up6arrow-down1·1 day agoMaybe updating everything brought in a new supply chain attack and you just infected yourself I only run updates that are old for this very reason (unless there’s a very specific cve fix)
minus-squaresurewhynotlem@lemmy.worldlinkfedilinkEnglisharrow-up2·11 hours agoThis is my company’s strategy. Our tech is too old to be in scope of the latest vulns.
minus-squarenibbler@discuss.tchncs.delinkfedilinkEnglisharrow-up2·19 hours agoIt really is an issue for user driven repositories like aur and all those pypy, gems, composer stuff. For distribution controlled packages the risk is way lower.
minus-squareMuttMutt@lemmy.worldlinkfedilinkEnglisharrow-up2·21 hours agoOr maybe you just got hacked because you didn’t update. This line of thinking can go back and forth forever.
minus-squareryannathans@aussie.zonelinkfedilinkEnglisharrow-up1·16 hours agoSee above where I said if it’s for a cve it gets installed asap
Maybe updating everything brought in a new supply chain attack and you just infected yourself
I only run updates that are old for this very reason (unless there’s a very specific cve fix)
This is my company’s strategy. Our tech is too old to be in scope of the latest vulns.
It really is an issue for user driven repositories like aur and all those pypy, gems, composer stuff. For distribution controlled packages the risk is way lower.
Or maybe you just got hacked because you didn’t update.
This line of thinking can go back and forth forever.
See above where I said if it’s for a cve it gets installed asap