# CVE-2024-47850: Denial of service in n/a

> Attackers can trigger DDoS amplification by sending a single UDP packet, causing CUPS to send HTTP POST requests to arbitrary destinations.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Oct 2024
- **Updated:** 11 Oct 2024
- **Also known as:** AZL-53837, DEBIAN-CVE-2024-47850, GHSA-phc2-g348-384g, GHSA-rq86-c7g6-r2h8, SUSE-SU-2024:3756-1

## What is CVE-2024-47850?

CVE-2024-47850 is a high-severity denial of service vulnerability in n/a, published on 4 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CUPS 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.)

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2024-47850?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cups-filters` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 1.0.58-19.32.1 |
| `cups-filters` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 1.0.58-19.32.1 |

## How do I fix CVE-2024-47850?

Upgrade to a fixed version.

## Is CVE-2024-47850 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47850 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-47850 and fix it if it is affected.

What it is: CVE-2024-47850 is a high-severity denial of service vulnerability in n/a, published on 4 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47850 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-47850/ (Markdown: https://insights.sbomify.com/CVE-2024-47850/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-47850
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-47850
- OSV: https://osv.dev/vulnerability/CVE-2024-47850

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-47850/
Summaries are generated and may contain mistakes; the official description above is the record.