BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-47175High confidence

libppd's ppdCreatePPDFromIPP2 function does not sanitize IPP attributes when creating the PPD buffer

OpenPrinting · libppd

Official source article: GitHub GHSA-7XFX-47QG-GRP6 ↗. Check the applicable product and release in the original source.

8.6HighCVSS 3.1
Recommended action
Within 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Critical, raised one band.upgradedsince 3 Nov 2025

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 63.61% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs OpenPrinting libppd and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

10 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · maincupsVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.2.4.10-r1Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · maincupsVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.2.4.10-r1Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · maincupsVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.2.4.10-r1Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcecupsVendor fix publishedDebian records a fixed source-package version for this release.2.4.10-2Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcecupsVendor fix publishedDebian records a fixed source-package version for this release.2.4.2-3+deb12u8Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelibppdNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcecupsVendor fix publishedDebian records a fixed source-package version for this release.2.4.10-2Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcecupsVendor fix publishedDebian records a fixed source-package version for this release.2.4.10-2Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivecupsVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.2.4.7-1.2ubuntu7.3Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelibppdVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.2:2.0.0-0ubuntu4.1Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-42297

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

CUPS is a standards-based, open-source printing system, and `libppd` can be used for legacy PPD file support. The `libppd` function `ppdCreatePPDFromIPP2` does not sanitize IPP attributes when creating the PPD buffer. When used in combination with other functions such as `cfGetPrinterAttributes5`, can result in user controlled input and ultimately code execution via Foomatic. This vulnerability can be part of an exploit chain leading to remote code execution (RCE), as described in CVE-2024-47176.

What

CUPS is a standards-based, open-source printing system, and `libppd` can be used for legacy PPD file support. The `libppd` function `ppdCreatePPDFromIPP2` does not sanitize IPP attributes when creating the PPD buffer. When used in combination with other functions such as `cfGetPrinterAttributes5`, can result in user controlled input and ultimately code execution via Foomatic. This vulnerability can be part of an exploit chain leading to remote code execution (RCE), as described in CVE-2024-47176.

Why

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.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

What

CUPS is a standards-based, open-source printing system, and `libppd` can be used for legacy PPD file support. The `libppd` function `ppdCreatePPDFromIPP2` does not sanitize IPP attributes when creating the PPD buffer. When used in combination with other functions such as `cfGetPrinterAttributes5`, can result in user controlled input and ultimately code execution via Foomatic. This vulnerability can be part of an exploit chain leading to remote code execution (RCE), as described in CVE-2024-47176.

Why

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.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Improper Input Validation → execute code or commands in the affected security context
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-20 ↗

CWE-20: Improper Input Validation. 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.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CNoneConfidentiality impact: No direct loss is represented by this metric.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
NetworkUnauthenticatedRemote code executionCWE-20Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2024-2240CUPS: Mehrere Schwachstellen ermöglichen Ausführung von beliebigem Programmcode

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in CUPS ausnutzen, um beliebigen Programmcode mit den Rechten des Dienstes auszuführen und um Informationen offenzulegen.

Official advisory ↗
Canadian Centre for Cyber Security · English · AV24-551OpenPrinting CUPS security advisory (AV24-551)

On September 26, 2024, OpenPrinting published security updates to address vulnerabilities in the following product:

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20241002Security Bulletin 02 Oct 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 02 Oct 2024, published on 2 October 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0924Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-27268 Référence CVE CVE-2024-27270 https://www.cve.org/CVERecord?id=CVE-2024-27270 Référence CVE CVE-2024-29857 https://www.cve.org/CVERecord?id=CVE-2024-29857 Référence CVE CVE-2024-38819 https://www.cve.org/CVERecord?id=CVE-2024-38819 Référence CVE CVE-2024-38821 https://www.cve.org/CVERecord?id=CVE-2024-38821 Référence CVE CVE-2024-45296 https://www.cve.org/CVERecord?id=CVE-2024-45296 Référence CVE CVE-2024-45338 https://www.cve.org/CVERecord?id=CVE-2024-45338 Référence CVE CVE-2024-45801 https://www.cve.org/CVERecord?id=CVE-2024-45801 Référence CVE CVE-2024-47076 https://www.cve.org/CVERecord?id=CVE-2024-47076 Référence CVE CVE-2024-47175 https://www.cve.org/CVERecord?id=CVE-2024-47175 Référence CVE CVE-2024-47176 https://www.cve.org/CVERecord?id=CVE-2024-47176 Référence CVE CVE-2024-47177 https://www.cve.org/CVERecord?id=CVE-2024-47177 Référence CVE CVE-2024-47535 https://www.cve.org/CVERecord?id=CVE-2024-47535 Référence CVE CVE-2024-53382 https://www.cve.org/CVERecord?id=CVE-2024-53382 Référence CVE CVE-2024-55565 https://www.cve.org/CVERecord?id=CVE-2024-55565 Référence CVE CVE-2025-21587 https://www.cve.org/CVERecord?id=CVE-2025-21587 Référence CVE CVE-2025-22228 https://www.cve.org/CVERecord?id=CVE-2025-22228 Référence CVE CVE-2025-22235 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0512Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2024-37529 Référence CVE CVE-2024-41091 https://www.cve.org/CVERecord?id=CVE-2024-41091 Référence CVE CVE-2024-41123 https://www.cve.org/CVERecord?id=CVE-2024-41123 Référence CVE CVE-2024-41946 https://www.cve.org/CVERecord?id=CVE-2024-41946 Référence CVE CVE-2024-45296 https://www.cve.org/CVERecord?id=CVE-2024-45296 Référence CVE CVE-2024-45337 https://www.cve.org/CVERecord?id=CVE-2024-45337 Référence CVE CVE-2024-45338 https://www.cve.org/CVERecord?id=CVE-2024-45338 Référence CVE CVE-2024-4603 https://www.cve.org/CVERecord?id=CVE-2024-4603 Référence CVE CVE-2024-47076 https://www.cve.org/CVERecord?id=CVE-2024-47076 Référence CVE CVE-2024-47175 https://www.cve.org/CVERecord?id=CVE-2024-47175 Référence CVE CVE-2024-47176 https://www.cve.org/CVERecord?id=CVE-2024-47176 Référence CVE CVE-2024-47177 https://www.cve.org/CVERecord?id=CVE-2024-47177 Référence CVE CVE-2024-47535 https://www.cve.org/CVERecord?id=CVE-2024-47535 Référence CVE CVE-2024-47561 https://www.cve.org/CVERecord?id=CVE-2024-47561 Référence CVE CVE-2024-49761 https://www.cve.org/CVERecord?id=CVE-2024-49761 Référence CVE CVE-2024-51744 https://www.cve.org/CVERecord?id=CVE-2024-51744 Référence CVE CVE-2024-52046 https://www.cve.org/CVERecord?id=CVE-2024-52046 Référence CVE CVE-2024-52798 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1081Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-42459 Référence CVE CVE-2024-42460 https://www.cve.org/CVERecord?id=CVE-2024-42460 Référence CVE CVE-2024-42461 https://www.cve.org/CVERecord?id=CVE-2024-42461 Référence CVE CVE-2024-43796 https://www.cve.org/CVERecord?id=CVE-2024-43796 Référence CVE CVE-2024-43799 https://www.cve.org/CVERecord?id=CVE-2024-43799 Référence CVE CVE-2024-43800 https://www.cve.org/CVERecord?id=CVE-2024-43800 Référence CVE CVE-2024-45296 https://www.cve.org/CVERecord?id=CVE-2024-45296 Référence CVE CVE-2024-45491 https://www.cve.org/CVERecord?id=CVE-2024-45491 Référence CVE CVE-2024-45590 https://www.cve.org/CVERecord?id=CVE-2024-45590 Référence CVE CVE-2024-47175 https://www.cve.org/CVERecord?id=CVE-2024-47175 Référence CVE CVE-2024-47554 https://www.cve.org/CVERecord?id=CVE-2024-47554 Référence CVE CVE-2024-47764 https://www.cve.org/CVERecord?id=CVE-2024-47764 Référence CVE CVE-2024-48949 https://www.cve.org/CVERecord?id=CVE-2024-48949 Référence CVE CVE-2024-51504 https://www.cve.org/CVERecord?id=CVE-2024-51504 Référence CVE CVE-2024-52316 https://www.cve.org/CVERecord?id=CVE-2024-52316 Référence CVE CVE-2024-52317 https://www.cve.org/CVERecord?id=CVE-2024-52317 Référence CVE CVE-2024-52318 https://www.cve.org/CVERecord?id=CVE-2024-52318 Référence CVE CVE-2024-5535 https://www.cve.org/CVERecord?id=C

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-028483OpenPrinting の libppd 等複数ベンダの製品における脆弱性

OpenPrinting の libppd 等複数ベンダの製品には、不特定の脆弱性が存在します。

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-6298CUPS 제품 보안 조치 권고

libppd의 PPD 파일 생성 취약점 (CVE-2024-47175)[3]

Official advisory ↗
NCSC-NL · Dutch · NCSC-2024-0384Kwetsbaarheden ontdekt in CUPS

Door een aaneenschakeling van de vier kwetsbaarheden, kan een kwaadwillende onder bepaalde omstandigheden willekeurige code uitvoeren binnen de context van de CUPS-service.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
libppd: <= 2.1b1
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 26 Sept 2024 · Last source change 3 Nov 2025, 22:20 UTC · CWE-20 · Improper Input Validation

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-42297
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-42297↗CISA Vulnrichment SSVC evidence↗Public exploit reference · GitHub GHSA-7XFX-47QG-GRP6↗Patch or update reference↗Public exploit reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-47175 · cve.blacktree.nl