# CVE-2006-7221: Integer overflow in n/a

> Attackers can cause a denial of service in fsplib via off-by-one errors in name and d_name entry attributes.

- **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:** 25 Jul 2007
- **Updated:** 3 Apr 2025
- **Also known as:** DEBIAN-CVE-2006-7221, GHSA-58qj-mg92-jx36

## What is CVE-2006-7221?

CVE-2006-7221 is a high-severity vulnerability in n/a, published on 25 Jul 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple off-by-one errors in fsplib.c in fsplib before 0.8 allow attackers to cause a denial of service via unspecified vectors involving the (1) name and (2) d_name entry attributes.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Fsp C Library.

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

Upgrade to a fixed version.

## Is CVE-2006-7221 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-3962](https://insights.sbomify.com/CVE-2007-3962/): Memory corruption in n/a (high 7.5)
- [CVE-2007-3961](https://insights.sbomify.com/CVE-2007-3961/): Off-by-one error in the fsp_readdir_r function in fsplib.c in fsplib before 0.9 allows remote attackers to cause a denial of service via a d (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-7221 is a high-severity vulnerability in n/a, published on 25 Jul 2007. 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-2006-7221 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-2006-7221/ (Markdown: https://insights.sbomify.com/CVE-2006-7221/index.md)
```

## Sources

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

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