CVE-2024-47076VulnerabilityPublished 2 Oct 2024Updated 5 Nov 2026

Red Hat Security Advisory: cups-filters security update

Affects Red Hat cups-filtersSource GCVE Database

Compare

Authoritative record:CVE-2024-47076· High 8.6

Public exploit available (Metasploit) · CVSS 8.6 High.

Data as of 5 Nov 2026, 15:05 UTC

CVSS 3.1 base score

8.6High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	8.6

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Sep 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
1 Metasploit module
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Red Hat has released updated packages for cups-filters addressing these vulnerabilities. Users of affected Red Hat Enterprise Linux 8.4 variants should apply the security update as detailed in Red Hat advisory RHSA-2024:7504. The vendor advisory provides instructions for applying the update. Since a fix is available, applying the update is the recommended mitigation.

Description

A security update for the cups-filters package addresses multiple vulnerabilities including an issue in the libcupsfilters cfGetPrinterAttributes API that fails to sanitize returned IPP attributes (CVE-2024-47076). Additional fixes cover a cups-browsed UDP binding flaw and a remote command injection vulnerability in cups libppd. These issues affect Red Hat Enterprise Linux 8.4 variants and have been rated with an Important security impact by Red Hat. Public exploit code is available via Metasploit for CVE-2024-47076.

Impact

The vulnerabilities could allow an attacker to exploit unsanitized IPP attributes, potentially leading to unauthorized actions or code execution. The presence of public exploit code for CVE-2024-47076 increases the risk of exploitation. The remote command injection vulnerability in cups libppd could allow execution of arbitrary commands. The cups-browsed UDP binding flaw could expose the service to unauthorized requests. Red Hat rates the overall security impact as Important.

Summary

The cups-filters package, formerly part of the core CUPS distribution, contains multiple security flaws. Notably, CVE-2024-47076 involves the libcupsfilters cfGetPrinterAttributes API not sanitizing IPP attributes, potentially allowing malicious input to be processed. Other vulnerabilities include cups-browsed binding to UDP INADDR_ANY:631 and trusting any packet source, and a remote command injection via attacker-controlled data in PPD files within cups libppd. Red Hat has issued security updates for these issues affecting RHEL 8.4 variants. Metasploit exploit code exists for CVE-2024-47076, indicating potential for exploitation.

CWE-20Improper Input Validation (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #18OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Attack Surface Reduction
Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build "recognizers" for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of…
Architecture and Design · Libraries or Frameworks
Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Server Side Include (SSI) Injection (opens in a new tab)
Cross Zone Scripting (opens in a new tab)
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-77Improper Neutralization of Special Elements used in a Command (Command Injection) (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #23OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
Architecture and Design
If at all possible, use library calls rather than external processes to recreate the desired functionality.
Implementation
If possible, ensure that all external commands called from the program are statically created.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
Attack patterns
LDAP Injection (opens in a new tab)
Command Delimiters (opens in a new tab)
IMAP/SMTP Command Injection (opens in a new tab)
Manipulating Writeable Terminal Devices (opens in a new tab)
Exploiting Multiple Input Interpretation Layers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-940Improper Verification of Source of a Communication Channel (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product establishes a communication channel to handle an incoming request that has been initiated by an actor, but it does not properly verify that the request is coming from the expected origin.
Architecture and Design
Use a mechanism that can validate the identity of the source, such as a certificate, and validate the integrity of data to ensure that it cannot be modified in transit using an Adversary-in-the-Middle (AITM) attack.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V1.14.1 (opens in a new tab)
V14.5.2 (opens in a new tab)
V14.5.3 (opens in a new tab)
Attack patterns
WebView Injection (opens in a new tab)
Connection Reset (opens in a new tab)
TCP RST Injection (opens in a new tab)
Traffic Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 5 Nov 2026, 15:05 UTC

Public exploits and detection1 Metasploit module, GitHub proofs of concept

WeaknessesCWE-20, CWE-77, CWE-940

Technical details

References

Community reviews

Related threats