CVE-2024-47176

Published Sep 26, 2024

Last updated a year ago

CVSS medium 5.3
Ubuntu

Overview

Description
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 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.
Source
security-advisories@github.com
NVD status
Modified
Products
cups-browsed

Risk scores

CVSS 3.1

Type
Secondary
Base score
5.3
Impact score
1.4
Exploitability score
3.9
Vector string
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Severity
MEDIUM

Weaknesses

security-advisories@github.com
CWE-1327

Social media

Hype score
Not currently trending

  1. 🔴En este vídeo vamos a explotar la vulnerabilidad CUPS Command Injection (CVE-2024-47176) que nos permite inyectar comandos instalando una impresora maliciosa a través del puerto UDP 631. ¡Espero que os resulte útil! 🥷 👇👇👇 https://t.co/2HBZkcqRf4 https://t.co/2HBZkcqRf4 ht

    @xerosec

    148 Impressions

    1 Retweet

    8 Likes

    1 Bookmark

    0 Replies

    0 Quotes

  2. CVE-2024-47176, CVE-2024-47076, CVE-2024-47175, CVE-2024-47177: Linux OpenPrinting CUPS RCE GitHub.. https://t.co/J2CFFT1Qhx For more information about CUPS.(Printing system remote execution.. 👇 https://t.co/ELv0lGyaYU #CVE

    @un_exceptional

    13 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    2 Replies

    0 Quotes

  3. Actively exploited CVE : CVE-2024-47176

    @transilienceai

    11 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    1 Reply

    0 Quotes

  4. Our latest research reveals a critical #CUPS vulnerability chain, enabling unauthenticated Remote Code Execution (RCE). We explain how CVE-2024-47176 and others can be exploited worldwide. 👉 Learn more from the Ostorlab team: https://t.co/jjD40TE83h #cybersecurity #infosec #CVE

    @OstorlabSec

    108 Impressions

    3 Retweets

    5 Likes

    2 Bookmarks

    0 Replies

    0 Quotes

  5. ثغرات متعددة في CUPS تتيح تنفيذ التعليمات البرمجية عن بُعد على نظام #Linux 1) cve-2024-47076 2) CVE-2024-47175 3) CVE-2024-47176 4) CVE-2024-47177 استعلام #Criminal_IP ✅title: CUPS port:631 ✅title: Home - CUPS port:631 https://t.co/TwVHxOmvB7 https://t.co/Dml9z1YZ7F

    @CriminalIP_AR

    1 Impression

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  6. CVEs Explainer #9 CVE-2024-47176 (CUPS Remote Code Execution) A chain of vulnerabilities in the Common Unix Printing System (CUPS). The cups-browsed service trusted any packet from any source, allowing an attacker to replace a printer's IPP URL with a malicious one and achieve

    @xbhaveshverma

    8 Oct 2026

    65 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  7. How have we never removed CUPS (Commun Unix Printing System) from being included by default on Ubuntu images. "It's just leftover" even after 2024 CVE-2024-47176 https://t.co/XHAEevc2Db

    @telep_io

    15 Feb 2026

    74 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  8. Cytellite recent detection targeting CVE-2024-47176 — HURRICANE Visit -- https://t.co/k7adI6yVO5 #Loginsoft #Cytellite #Cybersecurity #CVE202447176 #LOVI #ThreatIntelligence #Infosecurity #AI https://t.co/I4dtduwArs

    @Loginsoft_Intel

    2 Jan 2026

    59 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  9. Cytellite recent detection targeting CVE-2024-47176 — CENSYS-ARIN-01 visit -- https://t.co/9fKptzvp1g #LoginSoft #Cytellite #CyberSecurity #CVE-2024-47176 #lovi #threatintelligence #infosecurity #Ai https://t.co/xKMjd4MWEV

    @Loginsoft_Intel

    16 Dec 2025

    6 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  10. Critical RCE flaws in Linux CUPS (CVE-2024-47176–47177) expose 75K+ servers to attacks, letting hackers run malicious code via print services. Update to secure your systems! Follow @ElusivePrivacy for updates & stay safe. Source: https://t.co/gN9wD3B5t9

    @ElusivePrivacy

    14 May 2025

    27 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  11. Our experts regularly update Core Impact's certified #exploit library. Get details on the latest additions, including CVE-2024-6769, CVE-2024-36401, CVE-2024-47176, CVE-2024-38054, CVE-2024-26230, CVE-2024-0799, CVE-2024-0800, and more. https://t.co/DziZgG9ccw https://t.co/gveK7y

    @CoreSecurity

    11 Nov 2024

    401 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  12. "Cracking open the 'CUPS of chaos' with CVE-2024-47176. One crafty packet punches a 600x DDoS amplification. Still running 2007's CUPS version? @CyberSecPro, surely not! Patch or prepare for a botnet brewing in your backyard. #CyberSecurity #DDoS #UnixVulnerability #TimeToPatch"

    @LimitedViewX

    10 Nov 2024

    53 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  13. Actively exploited CVE : CVE-2024-47176

    @transilienceai

    23 Oct 2024

    10 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    1 Reply

    0 Quotes

  14. Actively exploited CVE : CVE-2024-47176

    @transilienceai

    20 Oct 2024

    11 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    1 Reply

    0 Quotes

Configurations

Related CVEs

  1. Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary.•CVE-2026-84782
  2. ZoneMinder versions 1.37.0 before 1.38.0 contain a path traversal vulnerability in the files view that allows authenticated users to read arbitrary files. The path parameter is not properly validated before being passed to output_file, enabling attackers with Events view permission to access sensitive files like configuration files containing database credentials.•CVE-2024-58386
  3. WordPress Core Remote File Inclusion Vulnerability•CVE-2026-87902
  4. Google Chromium V8 Type Confusion Vulnerability•CVE-2026-85046
  5. In the Linux kernel, the following vulnerability has been resolved: net: gro: properly validate BIG TCP aggregation criteria When GRO attempts to aggregate packets beyond GRO_LEGACY_MAX_SIZE (64KB), BIG TCP should only be permitted for plain IPv4 TCP and plain IPv6 TCP (with sufficient MAC header room to insert the temporary HBH jumbo header). However, commit b1a78b9b9886 ("net: add support for ipv4 big tcp") loosened the check in skb_gro_receive(), leading to several issues: 1. skb_gro_receive() checked skb_headroom(p) instead of the actual space before the MAC header (p->mac_header). Because skb_headroom(p) includes mac_len, crafted frames (e.g. injected via AF_PACKET) can pass the check with p->mac_header < 8 bytes. When ipv6_gro_complete() inserts the temporary HBH jumbo header, the memmove() starts before skb->head, causing an out-of-bounds write and wrapping skb->mac_header. 2. It allowed non-IP protocols such as software VLAN (ETH_P_8021Q / ETH_P_8021AD) to aggregate beyond 64KB because p->protocol != ETH_P_IPV6 was true. 3. It checked p->encapsulation instead of NAPI_GRO_CB(skb)->encap_mark, allowing encapsulated flows (e.g. SIT / IPv6-in-IPv4) to aggregate beyond 64KB. Fix skb_gro_receive() to strictly enforce: - NAPI_GRO_CB(skb)->proto == IPPROTO_TCP - Not encapsulated (!NAPI_GRO_CB(skb)->encap_mark && !p->encapsulation) - Protocol must be either ETH_P_IP or ETH_P_IPV6 - If ETH_P_IPV6, p->mac_header must be at least sizeof(struct hop_jumbo_hdr) Returning -E2BIG from skb_gro_receive() ensures that packets which cannot become BIG TCP are cleanly flushed at <= 64KB and delivered intact without dropping. This issue does not exist in mainline (7.0+) because the subsystem was rewritten in commit 81be30c1f5f2 ("net/ipv6: Drop HBH for BIG TCP on RX side"), making this fix relevant only for older stable branches like 6.18.y.•CVE-2026-80725

References

Sources include official advisories and independent security research.