Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2024-47175: IPP Attribute Injection in libppd ppdCreatePPDFromIPP2

Published Sep 26, 2024 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS63.6%99th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendors
Debian ProjectOpenprinting
IdentifiersCVE-2024-47175CWE-20 · Improper Input Validation

CVE-2024-47175 is an improper input-validation vulnerability in libppd through version 2.1b1. The ppdCreatePPDFromIPP2 function fails to validate or sanitize Internet Printing Protocol (IPP) attributes while writing a temporary PostScript Printer Description (PPD) file. An attacker-controlled IPP service can therefore inject data into the generated PPD. In combination with other vulnerable CUPS printing-stack behavior, including retrieval of malicious printer attributes and Foomatic processing, the flaw can contribute to remote 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.

CVE-2024-47175 can enable attacker control of generated PPD content. As part of the disclosed CUPS exploit chain, malicious PPD directives can cause Foomatic to execute attacker-supplied commands after a victim submits a job to an attacker-controlled printer. Execution is generally in the context of the unprivileged lp account, limiting access to privileged operations and properly protected user data, but it can still permit compromise of data and resources accessible to that account.

Mitigation

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

Where printer auto-discovery is not required, disable or remove cups-browsed. On systems where it must remain installed, configure BrowseRemoteProtocols to none and restart cups-browsed. Restrict exposure of UDP port 631 and block untrusted Zeroconf, mDNS, and DNS-SD printer-discovery traffic. Constrain the lp service account using mandatory-access-control and network policies to reduce the impact of command execution.

Remediation

Patch, then assume compromise.

Install vendor-provided security updates for affected libppd, cups-filters, and related CUPS packages. Red Hat issued fixes for supported RHEL 7, 8, and 9 streams through cups-filters advisories; other distributions should apply their corresponding maintained package updates. RHEL 6 is out of support and is not receiving a fix.

Public exploits

Exploits

2 exploits validated by Mallory's analysis.

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 · networkWeaponizedCups-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 · fileOperational
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
Debian ProjectDebian Linuxoperating_system
OpenprintingLibppdapplication
FAQ

Frequently asked questions

Is CVE-2024-47175 exploited in the wild?
Yes. As of Oct 2, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2024-47175?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2024-47175, the earliest disclosed Sep 26, 2024.
Is there a patch for CVE-2024-47175?
Install vendor-provided security updates for affected libppd, cups-filters, and related CUPS packages. Red Hat issued fixes for supported RHEL 7, 8, and 9 streams through cups-filters advisories; other distributions should apply their corresponding maintained package updates.
What products are affected by CVE-2024-47175?
Openprinting Libppd and Debian Project Debian Linux.
How severe is CVE-2024-47175?
CVE-2024-47175 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 63.6% (99th percentile) as of Oct 2, 2026.
Activity feed

Recent activity

25 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+19 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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 signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.