Technology

37800 readers

478 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

[email protected]

Critical Unauthenticated RCE Flaws in CUPS Printing Systems (blog.qualys.com)

submitted 2 months ago by [email protected] to c/[email protected]

6 comments fedilink hide all child comments

top 6 comments

sorted by: hot top controversial new old

[–] [email protected] 7 points 2 months ago* (last edited 2 months ago) (1 children)

Exploitation involves sending a malicious UDP packet to port 631 on the target, directing it to an attacker-controlled IPP server.

Okay, so at least until this is patched, it would be a good idea to shut down any CUPS-related process that's listening on port 631, and avoid interaction with untrusted or potentially compromised print servers.

Either of these commands will list such processes:

$ sudo lsof -i :631

$ sudo fuser -v 631/tcp 631/udp

I don't want to diminish the urgency of this vulnerability, but it is worth noting that "affecting all GNU/Linux systems" does not mean that every affected system is actually running the vulnerable code. Some installations don't run print services and don't ever communicate with printers.

Also, I suspect that the author's use of "GNU" in that warning is misleading, potentially giving a false sense of security. (Sadly, a certain unfortunate meme has led many people to think that all Linux systems are GNU systems, and the author appears to be among them.) I don't see any reason to think musl builds of CUPS are immune, for example, so I don't assume my Alpine systems are safe just because they are not GNU/Linux.

[–] [email protected] 2 points 2 months ago (1 children)

What are your thoughts on the alternative path the article talks about "...zeroconf, mDNS, or DNS-SD advertisements"?

[–] [email protected] 2 points 2 months ago* (last edited 2 months ago) (1 children)

That refers to the fact that printer advertisements can contain lies: When you see a familiar printer name appear on a network, it could always be an impostor secretly pointing to the address of a malicious device.

So my first advice stands: Avoid interaction with untrusted or potentially compromised print servers.

To be clear, when I say "interaction", I don't just mean printing to them. I mean any interaction at all. Even just browsing a network for printers could potentially mean your system contacts the devices at the advertised addresses, and receives data from them. This Qualys report doesn't make clear whether this kind of interaction is safe, so I have to assume for now that it is not.

[–] [email protected] 2 points 2 months ago (1 children)

How do you avoid interaction if it's being done automatically by your machine when you open up a print dialog, and if malicious servers can use the same names as legit printers?

[–] [email protected] 2 points 2 months ago (1 children)

I suppose I would avoid connecting to untrusted networks, or avoid opening print dialogs while on them, or uninstall CUPS until a fix is available.

[–] [email protected] 2 points 2 months ago

Just a heads-up: A fix is available. I got an update to libcups-filters last night.