CVE-2024-47176
Openprinting Cups-Browsed 2.0.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NSummary
CVE-2024-47176 is a medium-severity Binding to an Unrestricted IP Address (CWE-1327) vulnerability in Openprinting Cups-Browsed. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to CM-6 (Configuration Settings) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CUPS, the open-source printing system, is affected in its cups-browsed component, which provides network printing features such as auto-discovery of print services. The vulnerability stems from cups-browsed binding to INADDR_ANY:631, which causes it to trust packets from any source and issue Get-Printer-Attributes IPP requests to an arbitrary attacker-controlled URL. This issue is tracked under CWE-1327 and carries a CVSS 3.1 score of 5.3.
An unauthenticated attacker with network access can exploit the flaw by supplying a malicious printer definition. When combined with the related issues CVE-2024-47076, CVE-2024-47175, and CVE-2024-47177, the weakness enables remote arbitrary command execution on the target system simply by causing a print job to be processed against the attacker-controlled printer.
Public advisories published by the OpenPrinting project on GitHub detail the affected code in cups-browsed and the companion libraries cups-filters, libcupsfilters, and libppd. The current EPSS score of 0.8759 matches its recorded peak, indicating sustained exploitation interest following disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-42298
Vulnerability Data
CUPS is a standards-based, open-source printing system, and `cups-browsed` contains network printing functionality including, but not limited to, auto-discovering print services and shared printers. `cups-browsed` binds to `INADDR_ANY:631`, causing it to trust any packet from any source, and can cause…
more
the `Get-Printer-Attributes` IPP request to an attacker controlled URL. When combined with other vulnerabilities, such as CVE-2024-47076, CVE-2024-47175, and CVE-2024-47177, an attacker can execute arbitrary commands remotely on the target machine without authentication when a malicious printer is printed to.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Establishes the most restrictive configuration settings, which would require binding only to specific addresses rather than 0.0.0.0.
Enforces approved information flow policies that would disallow unrestricted remote bindings.
Enforces least functionality by prohibiting unnecessary network exposure such as unrestricted listening addresses.
Requires control of communications at external and key internal interfaces, preventing binding that accepts traffic from any source.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Configuration management enforces restricted bind addresses, covering the weakness completely but only one aspect of overall hardening.
Network protection controls directly prevent exposure via unrestricted binds while fixing the weakness addresses only one vector of unauthorized access.
Documenting authorized network flows informs correct bind decisions and reduces the chance of 0.0.0.0 usage.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security of network services includes hardening service bindings to prevent exposure on all interfaces.
Secure architecture principles discourage exposing services on all interfaces, though the control is broader than this single weakness.
Network security controls directly require restricting listening interfaces to specific addresses rather than 0.0.0.0.
Network segregation can limit the blast radius of an unrestricted binding but does not prevent the binding itself.
Secure coding guidance can catch hard-coded 0.0.0.0 bindings during development but is not the primary mitigation.