# CVE-2008-0596: Denial of service in n/a

> Remote attackers can cause a denial of service in CUPS by exhausting memory through repeated printer add/remove requests.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Feb 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8473-h2r9-j663

## What is CVE-2008-0596?

CVE-2008-0596 is a medium-severity denial of service vulnerability in n/a, published on 26 Feb 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Memory leak in CUPS before 1.1.22, and possibly other versions, allows remote attackers to cause a denial of service (memory consumption and daemon crash) via a large number of requests to add and remove shared printers.

Weakness: CWE-399

## Which versions are affected by CVE-2008-0596?

It affects 1 product.


Products: Easy Software Products Cups.

## How do I fix CVE-2008-0596?

Upgrade to a fixed version.

## Is CVE-2008-0596 being exploited?

There is no known exploitation of CVE-2008-0596 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2001-0194](https://insights.sbomify.com/CVE-2001-0194/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-5849](https://insights.sbomify.com/CVE-2007-5849/): Integer overflow in n/a (critical 9.3)
- [CVE-2004-1125](https://insights.sbomify.com/CVE-2004-1125/): Memory corruption in n/a (critical 9.3)
- [CVE-2002-0063](https://insights.sbomify.com/CVE-2002-0063/): Memory corruption in n/a (high 7.5)
- [CVE-2001-1332](https://insights.sbomify.com/CVE-2001-1332/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-0596 and fix it if it is affected.

What it is: CVE-2008-0596 is a medium-severity denial of service vulnerability in n/a, published on 26 Feb 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-0596 in the wild and no public exploit code.

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-2008-0596/ (Markdown: https://insights.sbomify.com/CVE-2008-0596/index.md)
```

## Sources

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

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