# CVE-2018-9252: Denial of service in n/a

> A reachable assertion in JasPer allows attackers to cause a denial of service via crafted input.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5x2c-7cwv-6fv6, UBUNTU-CVE-2018-9252

## What is CVE-2018-9252?

CVE-2018-9252 is a medium-severity denial of service vulnerability in Jasper Project Jasper, published on 4 Apr 2018. 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

JasPer 2.0.14 allows denial of service via a reachable assertion in the function jpc_abstorelstepsize in libjasper/jpc/jpc_enc.c.

Weakness: CWE-617 (Reachable Assertion)

## Which versions are affected by CVE-2018-9252?

It affects 1 product.


Products: Jasper Project Jasper.

## How do I fix CVE-2018-9252?

Upgrade to a fixed version.

## Is CVE-2018-9252 being exploited?

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

What it is: CVE-2018-9252 is a medium-severity denial of service vulnerability in Jasper Project Jasper, published on 4 Apr 2018. 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-2018-9252 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-2018-9252/ (Markdown: https://insights.sbomify.com/CVE-2018-9252/index.md)
```

## Sources

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

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