[-] _Nemo_@lemmy.ml 2 points 4 hours ago* (last edited 4 hours ago)

Thank you! While that does allay most security concerns, it does beg the question how useful such a vulnerability tracker is if it doesn't actually show any relevant vulnerabilies and you constantly have to second-guess what it says. Warning signs that aren't actually warnings because it's "just a false alarm" quickly teach personell to not take warnings seriously - unti, onel day, it's not a false alarm...

[-] _Nemo_@lemmy.ml 1 points 4 hours ago

Thanks for your detailed reply!

To make that happen, the attacker must [...] already have access to the server to upload and process the file, which means that security has already failed.

Do I correctly assume that by axis you mean shell or even root level access? If not, any of my regular users (turned rogue...) could upload a poisoned raw file which nextcloud would process to, for instance, generate a thumbnail.

13
submitted 6 hours ago by _Nemo_@lemmy.ml to c/selfhosted@lemmy.world

Apologies if this is a rookie question, but I keep wondering what the vulnerabilities section on DockerHub is trying to tell me. Take nextcloud images for instance: The most current images seem to list 3 critical and 22 severe vulnerabilities. Does that mean those vulns are part of the image? If so, why would anyone want to run this?

[-] _Nemo_@lemmy.ml 3 points 17 hours ago

Corporate-driven > community-driven distros

[-] _Nemo_@lemmy.ml 5 points 18 hours ago
[-] _Nemo_@lemmy.ml 6 points 18 hours ago

Is it Shitpost Saturday already?

_Nemo_

0 post score
0 comment score
joined 1 day ago