Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2024-47176: Unauthenticated Printer Discovery Injection in OpenPrinting cups-browsed

Published Sep 26, 2024 · Updated 14 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.3Medium · v3.1
EPSS50.6%99th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Openprinting
IdentifiersCVE-2024-47176CWE-20

CVE-2024-47176 is an improper input validation vulnerability in OpenPrinting cups-browsed versions up to and including 2.0.1. The daemon's legacy printer-discovery listener binds to UDP port 631 on all interfaces and accepts unauthenticated printer advertisements without adequately validating their source. A crafted advertisement can cause cups-browsed to issue an IPP Get-Printer-Attributes request to an attacker-controlled endpoint and process the returned printer configuration. This vulnerability provides an entry point for a CUPS exploitation chain involving malicious IPP attributes, generated printer descriptions, and command execution when a print job is submitted to the malicious printer. It does not independently provide arbitrary command execution.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An unauthenticated network attacker can redirect printer discovery to a malicious IPP server, enabling unauthorized addition or replacement of printer configurations. Combined with IPP attribute-validation and printer-description vulnerabilities, including CVE-2024-47076 and CVE-2024-47175, this can lead to arbitrary command execution when a user prints to the attacker-controlled printer. Execution typically occurs as the unprivileged lp account, with access constrained by filesystem permissions and applicable AppArmor or SELinux policies; root privileges are not inherently obtained.

Mitigation

If you can’t patch tonight, do this now.

Stop and disable or mask cups-browsed where automatic printer discovery is not required. Alternatively, set BrowseRemoteProtocols to none and restart the service to disable remote discovery. Block inbound UDP port 631 from untrusted networks and restrict untrusted mDNS/DNS-SD advertisements to reduce alternative discovery exposure. Constrain the lp account using mandatory access controls and network restrictions to limit the consequences of chained command execution.

Remediation

Patch, then assume compromise.

Apply the operating-system vendor's security updates addressing CVE-2024-47176 in cups-browsed or its distribution-specific package. Update the other affected CUPS components, including libcupsfilters, libppd, and cups-filters, to address the complete exploitation chain. Distribution fixes and backports are available, so use vendor advisory status rather than upstream version numbers alone to verify remediation. Remove cups-browsed if automatic network printer discovery is unnecessary.

Public exploits

Exploits

7 exploits validated by Mallory's analysis. Hidden: 9 rejected by Mallory's analysis as not a working exploit.

View more in app →
cups_ipp_remote_code_execution.rbThis repository contains a single Metasploit module: 'modules/exploits/multi/misc/cups_ipp_remote_code_execution.rb'. The module exploits several vulnerabilities in OpenPrinting CUPS and related components (cups-browsed, libcupsfilters, libppd, cups-filters) on Linux systems. It allows an attacker on the same LAN to advertise a malicious printer using mDNS (multicast DNS) to the address 224.0.0.251. When a victim sends a print job to this printer, the module delivers a payload via the IPP protocol, resulting in remote code execution as the 'lp' user on the victim's machine. The exploit does not require any open CUPS ports on the victim; only user interaction (sending a print job) is needed. The module references four CVEs (CVE-2024-47076, CVE-2024-47175, CVE-2024-47177, CVE-2024-47176) and is based on public research and exploits. The main attack vector is network-based, leveraging LAN multicast and HTTP/IPP services. The module is operational and allows for customizable payloads via the Metasploit framework.Disclosed Sep 26, 2024 · Framework: metasploit · ruby · networkWeaponizedCVE-2024-47176This repository provides a functional proof-of-concept (PoC) exploit for CVE-2024-47176, a critical unauthenticated remote code execution vulnerability in the cups-browsed service (version 2.0.1 and below) on GNU/Linux systems. The exploit is implemented in a single Python script (CVE-2024-47176.py) and leverages the ability of cups-browsed to auto-discover and trust network printers via IPP (Internet Printing Protocol) on port 631. The script sets up a malicious IPP printer server and advertises it on the network using Zeroconf/mDNS. When a vulnerable cups-browsed client discovers and interacts with this fake printer, the exploit can inject arbitrary commands (such as a reverse shell) into the printer's configuration, which are then executed on the target system. The payload can be provided as a direct command or as a file (e.g., rev.sh). The exploit requires the attacker to have network access to the target and for the target to attempt to print to the attacker's malicious printer. The repository also includes a detailed README with vulnerability background, usage instructions, and references. No detection scripts or fake code are present; the code is a real exploit with operational payload capability.l0n3m4n · Disclosed Oct 3, 2024 · python · networkOperationalCVE-2024-47176This repository contains an operational exploit for CVE-2024-47176, a remote command execution vulnerability in the CUPS (Common UNIX Printing System) cups-browsed component. The exploit consists of a Python script ('evilcups.py') and a README.md with usage instructions. The script sets up a malicious IPP (Internet Printing Protocol) server on the attacker's machine and sends a specially crafted UDP packet to the target's port 631 (IPP). This packet advertises the attacker's server as a printer, and when the target CUPS server connects back to retrieve printer attributes, the exploit delivers a payload via the 'printer-more-info' attribute, which can result in arbitrary command execution on the target. The attacker can supply any command, such as a reverse shell, to gain remote access. The exploit requires the target's port 631 to be accessible and the cups-browsed functionality to be enabled. The repository is well-structured, with clear instructions and a single Python exploit script as the main entry point.gumerzzzindo · Disclosed Oct 5, 2024 · python · markdown · networkOperationalCUPS-CVE-2024-47176This repository contains a single standalone Python exploit script, main.py, targeting CUPS and explicitly labeled for CVE-2024-47176. The script is not part of a larger framework. Its structure is simple but fully operational: it combines an attacker-hosted Flask web server, UDP trigger logic, malicious PPD generation, and a TCP reverse-shell listener into one file. Core exploit flow: (1) the script builds a malicious PPD containing a FoomaticRIPCommandLine directive; (2) that directive embeds a Python3 reverse shell one-liner that connects back to the attacker and launches /bin/sh -i; (3) a Flask app serves this PPD content to any incoming path, acting as the attacker-controlled IPP/HTTP endpoint; (4) the script sends crafted UDP packets to the target on port 631 to advertise or trigger use of the attacker-controlled printer URI; and (5) once the target processes the malicious printer definition and a print job is triggered, the reverse shell connects back to the attacker listener. Notable functions: ipp_handler() logs inbound requests and returns the malicious PPD; start_ipp_server() launches the Flask server; send_udp_trigger() sends two UDP payload variants to the target, one containing an ipp:// URI and another containing an http://.../printer URI; start_shell_listener() waits for the reverse shell and provides an interactive command loop; main() parses arguments, constructs the payload, starts the server/listener threads, sends the trigger, and prints operator instructions. The exploit’s main capability is remote code execution leading to an interactive reverse shell, contingent on the target CUPS environment accepting and executing the malicious PPD/foomatic-rip command path. The repository contains no detection-only logic, no obfuscation, and no additional modules or support files.Rhyru9 · Disclosed May 29, 2026 · python · network · webOperationalCups-RCE-ExploitRepository contains two distinct C++ utilities: a primary exploit (cups_rce_exploit.cpp with top-level README) and a defensive mitigation tool under Cups-Patcher/. The exploit is a standalone operational PoC for the September 2024 CUPS RCE chain. It implements a rogue TCP IPP server that listens on an attacker-specified IP/port, parses inbound IPP requests from cups-browsed, and returns crafted printer attributes. The key malicious behavior is injection of attacker-controlled content into the media-type-supported attribute, embedding a FoomaticRIPCommandLine directive and cupsFilter entry so the target eventually executes an arbitrary shell command via foomatic-rip. The exploit also supports optionally sending the initial UDP browse/discovery trigger to a target host on port 631, causing cups-browsed to connect back to the rogue IPP server. Payloads are user-supplied at runtime and may be passed directly or loaded from a file, making the exploit flexible but still basic rather than framework-grade. The repository structure is simple: 4 files total, with 2 code files and 2 README files. The main exploit entry point is cups_rce_exploit.cpp. The secondary tool, Cups-Patcher/cups_patcher.cpp, is not an exploit; it is a mitigation utility that disables cups-browsed, edits /etc/cups/cupsd.conf to disable browsing and bind to localhost, adds iptables/ip6tables rules blocking UDP 631, replaces foomatic-rip with a harmless stub, modifies /etc/hosts, creates backups, and supports restore/check/status style operations. This confirms the repository’s overall purpose is both offensive demonstration of the CUPS vulnerability chain and defensive hardening guidance. Notable network observables from the exploit include UDP 631 for the trigger, TCP 631 (or attacker-selected port) for the rogue IPP server, IPP URIs of the form ipp://ATTACKER:PORT/printers/NAME, and device URIs of the form socket://ATTACKER:PORT. Example payload observables in the README include reverse shell traffic to TCP 4444, file writes under /tmp, and retrieval of a second-stage script from http://192.168.1.50/backdoor.sh.Stickxx00 · Disclosed Jul 10, 2026 · cpp · markdown · network · fileOperationalcups-browse-exploit-detectionThis standalone educational toolkit demonstrates the insecure printer-discovery stage associated with CVE-2024-47176, rather than the complete 2024 CUPS remote-code-execution chain. cups_attack.py builds IPv4/UDP browse advertisements containing operator-selected printer URLs and sends them to UDP/631. Its four variants exercise full versus minimal fields, an unusual type bitmask and state, and an ipp:// URI. Operators can customize ports, printer names, packet counts, timing, and source-IP spoofing, and export transmitted packets to PCAP. The repository contains 23 files, including three Python programs and one Bash script. ipp_listener.py accepts callbacks, logs peer addresses and the first 200 received bytes, and returns an empty HTTP/IPP response. cups_detector.py supports live capture and offline PCAP analysis, allowlists, advertisement parsing, per-source rate tracking, and CSV/JSON alerts. Some detector source is truncated in the supplied content, limiting complete verification of its alert-generation logic. mitigation/mitigations.sh adds or removes UDP/631 INPUT firewall rules, creates a source allowlist, and stops or starts cups-browsed. Firewall placement and existing rule order matter, especially for Docker-published ports; source-IP allowlisting alone is also weaker when advertisements can be spoofed. The remaining files are documentation, dependency configuration, directory placeholders, and evidence: twelve CSV/JSON reports and two listener logs. Scapy >=2.5.0 is the only declared third-party dependency. The evidence reports one HIGH unauthorized-advertisement alert per variant and ten HIGH plus five MEDIUM repeated-discovery alerts for the flood. The normal report is empty. These results establish only the supplied lab observations, not broad detection accuracy. Callback logs show HTTP POST /printers/EVILPRINTER, application/ipp, and a CUPS/2.4.2 user-agent prefix. The README reports suppression after removing the victim's published Docker UDP/631 port; the post-mitigation log contains no callbacks, but the provided inventory contains no PCAPs for independent traffic verification. Detection limitations include fixed port-631 filtering, no callback monitoring on the demonstrated ports 8631 and 9100, IPv4-only inspection, and simplistic URI-host parsing. No malicious printer attributes, PPD injection, print-job execution, reverse shell, or persistence are implemented. CVE-2024-47076, CVE-2024-47175, and CVE-2024-47177 appear in documentation as related-chain or lab context, but their downstream exploitation is not implemented. The README's characterization of CVE-2024-47177 as rejected is not established by this source analysis. No original repository URL, git reference, or archive size was supplied; empty metadata and size 0 indicate unavailable values.Md-Nafiul-Hamim · Disclosed Nov 11, 2026 · python · bash · networkPoCcups-cve-2024-47176The supplied repository contains eight files: two Python tools, a README, a Scapy dependency specification, and four CSV evidence files. It is a standalone educational proof of concept, not a framework module. cups_attack.py builds a configurable HTTP printer URI and sends a single raw IPv4/UDP packet to the victim's port 631. It demonstrates the insecure discovery and attacker-directed callback behavior associated with CVE-2024-47176. Although the README references CVE-2024-47076, CVE-2024-47175, and CVE-2024-47177, the code does not implement those downstream exploitation stages or achieve code execution, and it does not provide a callback listener. cups_detector.py analyzes PCAP files or captures live traffic. It flags advertisements containing /printers/ whose HTTP host is not allowlisted, malformed browse messages, per-source announcement counts exceeding a configurable threshold, and TCP SYN packets from the configured CUPS server to ports other than 631. These are heuristics rather than vulnerability confirmation: ordinary outbound TCP traffic can trigger the connection rule, counts have no time window, and URL parsing is limited. Live capture also lacks explicit interruption handling to guarantee export after Ctrl+C. The evidence files contain zero normal-traffic alerts, two attack alerts, one mitigated-run advertisement alert without a callback alert, and nine variation alerts. The variation evidence flags the third announcement as repeated, whereas the supplied default threshold of 3 flags only counts greater than 3; a different runtime threshold could explain this. The README mentions packet captures and screenshots, but neither is present in the supplied eight-file listing. The recorded alerts support the claimed callback demonstration but cannot independently establish successful exploitation without the underlying captures. Repository URL, Git reference, and archive size were not supplied; empty strings and zero represent unavailable metadata.Kokila-Chandramohan · Disclosed Nov 12, 2026 · python · networkPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
OpenprintingCupsapplication
OpenprintingCups-Browsedapplication
FAQ

Frequently asked questions

Is CVE-2024-47176 exploited in the wild?
Yes. As of Nov 4, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2024-47176?
Yes. Mallory tracks 7 public exploits or proofs of concept for CVE-2024-47176, the earliest disclosed Sep 26, 2024.
Is there a patch for CVE-2024-47176?
Apply the operating-system vendor's security updates addressing CVE-2024-47176 in cups-browsed or its distribution-specific package. Update the other affected CUPS components, including libcupsfilters, libppd, and cups-filters, to address the complete exploitation chain.
What products are affected by CVE-2024-47176?
Openprinting Cups and Openprinting Cups-Browsed.
How severe is CVE-2024-47176?
CVE-2024-47176 has a CVSS v3.1 score of 5.3 (Medium) and an EPSS score of 50.6% (99th percentile) as of Nov 4, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.