Skip to main content
Mallory
← Back to News
internet-facing-service-vulnerabilityrapid-weaponizationproof-of-concept-releaseinternet-exposed-service

CUPS cups-browsed Flaw Chain Enables Remote Command Execution

Vulnerability Disclosure · 4 sources · Updated 2mo ago · First seen Sep 26, 2024

CUPS cups-browsed Flaw Chain Enables Remote Command Execution

A four-CVE chain affecting CUPS and its cups-browsed component allows unauthenticated attackers to trigger remote command execution on vulnerable Linux systems, with potential exposure for macOS hosts using CUPS. An attacker can send a crafted UDP packet to port 631, induce cups-browsed to retrieve data from an attacker-controlled IPP server, and inject malicious printer attributes into a temporary PPD file; execution occurs when a user submits a print job.

The resulting commands run as the lp user and may be constrained by the cupsd AppArmor profile. Internet-exposed CUPS services face the highest risk. Security teams should investigate unexpected UDP/631 traffic, untrusted or anomalous lp-owned files, foomatic-rip executions, and known proof-of-concept marker files; the attack was publicly disclosed with an RCE proof of concept before CVEs and patches were broadly available.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

5 events · Sep 5, 2024 – Sep 29, 2024
  1. Reported Apr 26, 20267mo ago

    CUPS vulnerability details reportedly leaked before fixes

    Vulnerability details were reportedly leaked before CVE assignments and patches were available, preceding the public disclosure.

    New Remote Code Execution (RCE) Vulnerabilities in CUPS for Linux: Threats and Mitigations
  2. Sep 29, 20242y ago

    Researchers observe suspicious UDP/631 probing after CUPS disclosure

    Wiz Threat Research and Datadog observed several IP addresses scanning or communicating with UDP port 631 following disclosure of the CUPS flaw chain. Wiz stated that no successful in-the-wild exploitation had been reported as of September 29, though the activity could represent malicious scanning or security research.

    OpenPrinting CUPS Vulnerabilities: Analysis of related CVEs | Wiz Blog
  3. Reported Sep 28, 20242y ago

    Elastic releases CUPS exploitation detection-rule updates

    Elastic released out-of-the-box detection-rule updates for supported Stack versions to identify possible CUPS exploitation, including suspicious shell execution, outbound connections, and file creation by foomatic-rip or its lp-owned child processes.

    Cups Overflow: When your printer spills more than Ink
  4. Sep 26, 20242y ago

    EvilSocket publicly discloses CUPS RCE chain and proof of concept

    Simone Margaritelli, known as EvilSocket, publicly disclosed the CUPS remote-code-execution chain and an RCE proof of concept. Exploitation begins with an unauthenticated UDP/631 request to cups-browsed and requires a user to submit a print job to trigger the injected command.

    New Remote Code Execution (RCE) Vulnerabilities in CUPS for Linux: Threats and Mitigations
  5. Sep 5, 20242y ago

    CUPS vulnerability chain reported to maintainers

    The CUPS/cups-browsed vulnerability chain was initially reported to maintainers. The chain includes flaws later tracked as CVE-2024-47176, CVE-2024-47076, CVE-2024-47175, and CVE-2024-47177.

    New Remote Code Execution (RCE) Vulnerabilities in CUPS for Linux: Threats and Mitigations
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.

Open in app →

Affected products

2 linked
Cups-BrowsedCups

Observables

8 linked

Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.

Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.