# CVE-2016-10248: Null dereference in n/a

> Remote attackers can cause a denial of service via a NULL pointer dereference in the JasPer image library when processing empty sequences.

- **Severity:** High 7.5 (`CVSS:3.0/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:** 15 Mar 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fwrx-6246-jgv9, UBUNTU-CVE-2016-10248

## What is CVE-2016-10248?

CVE-2016-10248 is a high-severity vulnerability in Jasper Project Jasper, published on 15 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The jpc_tsfb_synthesize function in jpc_tsfb.c in JasPer before 1.900.9 allows remote attackers to cause a denial of service (NULL pointer dereference) via vectors involving an empty sequence.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Jasper Project Jasper.

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

Upgrade to a fixed version.

## Is CVE-2016-10248 being exploited?

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

What it is: CVE-2016-10248 is a high-severity vulnerability in Jasper Project Jasper, published on 15 Mar 2017. 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-2016-10248 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-10248/ (Markdown: https://insights.sbomify.com/CVE-2016-10248/index.md)
```

## Sources

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

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