# CVE-2006-2906: Denial of service in n/a

> Remote attackers can cause a denial of service via CPU exhaustion by sending malformed GIF data to applications using the GD library.

- **Severity:** Medium 5.4 (`AV:N/AC:H/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jun 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-2906, DSA-1117, GHSA-hc5w-hw37-7qxf

## What is CVE-2006-2906?

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

### Official description

The LZW decoding in the gdImageCreateFromGifPtr function in the Thomas Boutell graphics draw (GD) library (aka libgd) 2.0.33 allows remote attackers to cause a denial of service (CPU consumption) via malformed GIF data that causes an infinite loop.

## Which versions are affected by CVE-2006-2906?

It affects 1 product.


Products: Thomas Boutell Graphics Draw Library.

## How do I fix CVE-2006-2906?

Upgrade to a fixed version.

## Is CVE-2006-2906 being exploited?

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

Public exploit code:

- GD Graphics Library 2.0.33 - Remote Denial of Service (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-2906 and fix it if it is affected.

What it is: CVE-2006-2906 is a medium-severity denial of service vulnerability in n/a, published on 8 Jun 2006. 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-2006-2906 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-2006-2906/ (Markdown: https://insights.sbomify.com/CVE-2006-2906/index.md)
```

## Sources

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

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