this post was submitted on 23 Apr 2026
130 points (95.1% liked)
Technology
84431 readers
5523 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
And if it's like a lot of security scans, most of the results are technically correct, but, within the context of the project, not something anyone's going to take the time to fix.
I don't mind leaving "technically correct" vulnerabilities in place while there's no known way to create an exploit. If you've got a vuln with a known exploit and are relying on "but nobody is ever going to actually try that on us" - then you're part of the problem, a big part.
It might be a config thing, but pretty often these scans will find issues which are only relevant on e.g. windows, when building a Linux container. Or the issue is in some XML parsing library in the base OS but the service never receives XML and isn't public facing anyway. Context matters.
One that I have to copy-paste over and over are vulnerabilities in the CUPS printer driver chain that don't apply because we don't print arbitrary things, we only print things that we create. Yeah, there's a vulnerability here in image-magick if you throw it such and such maliciously crafted... well, we only allow it to process our internally generated reports and there's no pathway for maliciously crafted input to reach it, so...