- 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
You must log in or register to comment.
As other articles pointed out, this is only a problem if:
- You expose port 631 to the internet.
- Why would anyone do that?
- You have a malicious actor on your trusted network.
- If so, you have bigger problems.
- You hit “Print” on a compromised network, such as a public library, while using CUPS.
Only the last one is potentially problematic for more people, and even then, the number of people using Linux is still very small. Some libraries don’t allow printing or only printing via their computers.
It’s good to know this flaw exists, but it doesn’t seem like a particularly concerning attack vector.
- You expose port 631 to the internet.
If there is ONE project that needs a rewrite in modern C++ OR Rust (or some other ‘safe’ language) it’s FUCKING CUPS
Please, Rust fanatics, do ONE good instead of rewriting GPL programs into a corpo-rat license
Wow look at that CUPS code and tell me with a straight face there aren’t 5 more similar vulnerabilities waiting to be found…
