CVE-2024-47850
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCUPS cups-browsed before 2.5b1 will send an HTTP POST request to an arbitrary destination and port in response to a single IPP UDP packet requesting a printer to be added, a different vulnerability than CVE-2024-47176. (The request is meant to probe the new printer but can be used to create DDoS amplification attacks.)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe cups-browsed service in CUPS before version 2.5b1 contains an improper input validation vulnerability where a single IPP UDP packet requesting printer discovery causes the service to send an HTTP POST request to an arbitrary destination and port. Attackers can abuse this behavior for DDoS amplification attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if cups-browsed is runningRun 'ps aux | grep cups-browsed' or 'systemctl status cups-browsed' to see if the service is activeAffected if cups-browsed process is running and the service is enabled
-
Determine installed CUPS versionRun 'cups-config --version' or check the package manager (dpkg -l cups | grep cups, rpm -q cups, etc.)Affected if version is below 2.5b1 (e.g., 2.4.x, 2.4.0, 2.3.x, etc.)
-
Verify UDP port 631 is listeningRun 'netstat -uan | grep 631' or 'ss -uan | grep 631' to check if the IPP UDP listener is bound to port 631Affected if UDP port 631 is open and listening (indicates cups-browsed is accepting IPP UDP packets)
-
Confirm cups-browsed configuration allows remote connectionsCheck /etc/cups/cups-browsed.conf for 'BrowseRemoteProtocols' and 'BrowseLocalProtocols' settings; verify if the service is bound to 0.0.0.0 or not explicitly restricted to localhostAffected if cups-browsed is configured to accept remote IPP broadcasts (BrowseRemoteProtocols includes 'ipp') and is bound to non-localhost interfaces
You are affected if cups-browsed is running, CUPS version is earlier than 2.5b1, and UDP port 631 is exposed to untrusted networks, as this allows attackers to trigger arbitrary HTTP POST requests from your system.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade cups-browsed to version 2.5b1 or later. As an interim control, filter inbound UDP traffic to port 631 from untrusted sources at the network perimeter.
cups-browsed version 2.5b1 or later
- Identify the cups-browsed package version installed on affected systems
- Upgrade cups-browsed to version 2.5b1 or later
- Verify the upgrade was successful by checking the installed version
- Ensure the system is updated with latest security patches
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47850 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-47850 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data