# CVE-2014-8137: Use after free in n/a

> Remote attackers can trigger a double free in JasPer via crafted JPEG 2000 images, potentially causing crashes or arbitrary code execution.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/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:** 24 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6c5f-g4r3-q34j, UBUNTU-CVE-2014-8137

## What is CVE-2014-8137?

CVE-2014-8137 is a medium-severity use after free vulnerability in Jasper Project Jasper, published on 24 Dec 2014. 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

Double free vulnerability in the jas_iccattrval_destroy function in JasPer 1.900.1 and earlier allows remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via a crafted ICC color profile in a JPEG 2000 image file.

## Which versions are affected by CVE-2014-8137?

It affects 2 products.


Products: Jasper Project Jasper, Redhat Enterprise Linux.

## How do I fix CVE-2014-8137?

Upgrade to a fixed version.

## Is CVE-2014-8137 being exploited?

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

## Other vulnerabilities in Jasper Project Jasper

- [CVE-2008-3522](https://insights.sbomify.com/CVE-2008-3522/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-3520](https://insights.sbomify.com/CVE-2008-3520/): Integer overflow in n/a (critical 9.3)
- [CVE-2015-8751](https://insights.sbomify.com/CVE-2015-8751/): Integer overflow in n/a (high 8.8)
- [CVE-2023-51257](https://insights.sbomify.com/CVE-2023-51257/): Memory corruption in n/a (high 7.8)
- [CVE-2016-8886](https://insights.sbomify.com/CVE-2016-8886/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-8137 and fix it if it is affected.

What it is: CVE-2014-8137 is a medium-severity use after free vulnerability in Jasper Project Jasper, published on 24 Dec 2014. 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-2014-8137 in the wild and no public exploit code.

Affected product: Jasper Project Jasper. 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-2014-8137/ (Markdown: https://insights.sbomify.com/CVE-2014-8137/index.md)
```

## Sources

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

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