# CVE-2025-8835: JasPer Image Color Space Conversion jas_image.c jas_image_chclrspc null pointer dereference

> A local attacker can cause a denial of service via null pointer dereference in JasPer's image color space conversion handler.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Aug 2025
- **Updated:** 12 Aug 2025
- **Also known as:** AZL-66162, GHSA-f4c9-2q5g-hq95, UBUNTU-CVE-2025-8835

## What is CVE-2025-8835?

CVE-2025-8835 is a medium-severity vulnerability in Jasper Project Jasper, published on 11 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in JasPer up to 4.2.5. Affected by this vulnerability is the function jas_image_chclrspc of the file src/libjasper/base/jas_image.c of the component Image Color Space Conversion Handler. The manipulation leads to null pointer dereference. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. The identifier of the patch is bb7d62bd0a2a8e0e1fdb4d603f3305f955158c52. It is recommended to apply a patch to fix this issue.

Weakness: CWE-476 (NULL Pointer Dereference), CWE-404 (Improper Resource Shutdown or Release)

## Which versions are affected by CVE-2025-8835?

It affects 1 product.


Products: Jasper Project Jasper.

## How do I fix CVE-2025-8835?

Apply the vendor's patch.

## Is CVE-2025-8835 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8835 exists.

## 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-2025-8835 and fix it if it is affected.

What it is: CVE-2025-8835 is a medium-severity vulnerability in Jasper Project Jasper, published on 11 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8835 exists.

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-2025-8835/ (Markdown: https://insights.sbomify.com/CVE-2025-8835/index.md)
```

## Sources

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

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