# CVE-2007-2721: Memory corruption in n/a

> Remote attackers can cause denial of service or potential code execution via malformed JPEG-2000 images processed by the JasPer library.

- **Severity:** Medium 4.3 (`AV:N/AC:M/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-2721, DSA-2036-1, GHSA-9pv6-4w7h-vppx

## What is CVE-2007-2721?

CVE-2007-2721 is a medium-severity memory corruption vulnerability in n/a, published on 16 May 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The jpc_qcx_getcompparms function in jpc/jpc_cs.c for the JasPer JPEG-2000 library (libjasper) before 1.900 allows remote user-assisted attackers to cause a denial of service (crash) and possibly corrupt the heap via malformed image files, as originally demonstrated using imagemagick convert.

## Which versions are affected by CVE-2007-2721?

It affects 1 product.


Products: Jasper Jpeg-2000 Jasper Jpeg-2000.

## How do I fix CVE-2007-2721?

Upgrade to a fixed version.

## Is CVE-2007-2721 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2721 and fix it if it is affected.

What it is: CVE-2007-2721 is a medium-severity memory corruption vulnerability in n/a, published on 16 May 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-2721 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-2007-2721/ (Markdown: https://insights.sbomify.com/CVE-2007-2721/index.md)
```

## Sources

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

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