# CVE-2016-9583: Memory corruption in jasper

> An out-of-bounds heap read in the Jasper library allows attackers to cause denial of service or potentially execute code via crafted input.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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:** 1 Aug 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3f3w-h3vg-6wx9

## What is CVE-2016-9583?

CVE-2016-9583 is a medium-severity memory corruption vulnerability in Jasper Project Jasper, published on 1 Aug 2018. 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

An out-of-bounds heap read vulnerability was found in the jpc_pi_nextpcrl() function of jasper before 2.0.6 when processing crafted input.

Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-125 (Out-of-bounds Read)

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

It affects 8 products.


Products: Jasper Project Jasper, Oracle Outside in Technology, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Eus, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Workstation.

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

Upgrade to a fixed version.

## Is CVE-2016-9583 being exploited?

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

What it is: CVE-2016-9583 is a medium-severity memory corruption vulnerability in Jasper Project Jasper, published on 1 Aug 2018. 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-9583 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-9583/ (Markdown: https://insights.sbomify.com/CVE-2016-9583/index.md)
```

## Sources

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

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