# CVE-2016-10249: Integer overflow in n/a

> Remote attackers can trigger a heap-based buffer overflow via crafted images, potentially leading to code execution or denial of service.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 Mar 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-w7m7-2vcc-wx3m, UBUNTU-CVE-2016-10249

## What is CVE-2016-10249?

CVE-2016-10249 is a high-severity vulnerability in Jasper Project Jasper, published on 15 Mar 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Integer overflow in the jpc_dec_tiledecode function in jpc_dec.c in JasPer before 1.900.12 allows remote attackers to have unspecified impact via a crafted image file, which triggers a heap-based buffer overflow.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2016-10249?

It affects 1 product.


Products: Jasper Project Jasper.

## How do I fix CVE-2016-10249?

Upgrade to a fixed version.

## Is CVE-2016-10249 being exploited?

There is no known exploitation of CVE-2016-10249 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-2016-10249 and fix it if it is affected.

What it is: CVE-2016-10249 is a high-severity vulnerability in Jasper Project Jasper, published on 15 Mar 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-10249 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-2016-10249/ (Markdown: https://insights.sbomify.com/CVE-2016-10249/index.md)
```

## Sources

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

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