- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
cross-posted from: https://lemmy.zip/post/23601247
I hope this goes without saying but please do not run this on machines you don’t own.
The good news:
- the exploit seems to require user action
The bad news:
Device Firewalls are ineffective against this
if someone created a malicious printer on a local network like a library they could create serious issues
it is hard to patch without breaking printing
it is very easy to create printers that look legit
even if you don’t hit print the cups user agent can reveal lots of information. This may be blocked at the Firewall
TLDR: you should be careful hitting print
Exactly. This is bad, for the 0.3% of the computing population that use Linux AND have CUPS installed AND actually print things.
Not exactly a prime target, compared to literally almost anything else. If I were going all-in on something after having gained access to someone’s local network, I’m 100% in on any exploit that lets me use an infostealer trojan to steal your session cookies, not fiddling around and hoping you print something.
(Patch your shit anyways, but there’s no need to freak out.)