There’s been talk of this unauthenticated RCE vulnerability coming with a CVSS 9.9 rating but none of the technical details were publicly known until it was made public just now at the top of the hour. Simone Margaritelli discovered this vulnerability and has shared a write-up around this potentially very impactful Linux vulnerability.

This vulnerability, fortunately, doesn’t affect the Linux kernel but rather CUPS… The print server commonly used on Linux systems and other platforms.

From Attacking UNIX Systems via CUPS, Part I:

“A remote unauthenticated attacker can silently replace existing printers’ (or install new ones) IPP urls with a malicious one, resulting in arbitrary command execution (on the computer) when a print job is started (from that computer).”

This remote code execution issue can be exploited across the public Internet via a UDP packet to port 631 without needing any authentication, assuming the CUPS port is open through your router/firewall. LAN attacks are also possible via spoofing zeroconf / mDNS / DNS-SD advertisements.

Besides CUPS being used on Linux distributions, it also affects some BSDs, Oracle Solaris, Google Chrome OS, and others.

As of writing there is no Linux fix available for this high profile security issue. In the meantime it’s recommended to disable and remove the “cups-browsed” service, updating CUPS, or at least blocking all traffic to UDP port 631.

  • schizo@forum.uncomfortable.business
    link
    fedilink
    English
    arrow-up
    73
    arrow-down
    1
    ·
    1 month ago

    I had a moment of actual laughter.

    I was expecting a kernel issue handling networking connections or SSH or who the fuck knows but… cups?

    Printers, they ruin everything.

    • henfredemars@infosec.pub
      link
      fedilink
      English
      arrow-up
      20
      ·
      1 month ago

      Loads of complex code exposed to an assumed trusted network is the model of printers. They’re going to be full of security issues.

      This stuff should be sandboxed and then never, ever exposed to the Internet.

      • schizo@forum.uncomfortable.business
        link
        fedilink
        English
        arrow-up
        10
        arrow-down
        1
        ·
        1 month ago

        I’m always befuddled how these things end up public on the internet. (I’m not really.)

        Like, it’s not like the printer is the one poking holes in your firewall while you sleep.*

        *If it is, then you should feel great shame, throw away anything more complicated than a pair of dull scissors, and get a job digging holes then filling them back in.