CVE-2016-2089
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe jas_matrix_clip function in jas_seq.c in JasPer 1.900.1 allows remote attackers to cause a denial of service (invalid read and application crash) via a crafted JPEG 2000 image.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceJasPer 1.900.1 contains an out-of-bounds read vulnerability in the jas_matrix_clip function in jas_seq.c. When processing a crafted JPEG 2000 image, the function performs an invalid memory read, causing the application to crash. This is a denial-of-service vulnerability exploitable remotely via malicious image files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.900.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if JasPer library is installedSearch for Jasper library files on the system. Common library names include libjasper.so (Linux) or jasper.dll (Windows). Use commands like 'find / -name "libjasper*"' on Linux or check system directories on Windows.Affected if No JasPer library files are found on the system, meaning the software is not present.
-
Determine installed JasPer versionCheck the version of the installed JasPer library. On Linux, you can use 'dpkg -l libjasper*' or 'rpm -qa | grep jasper'. On Windows, right-click the jasper DLL and view Properties > Details for version information. Compare the version number to 1.900.1.Affected if The installed version is exactly 1.900.1, as this is the only affected version listed.
-
Identify applications using JasPerReview application dependencies to find software that links against the JasPer library. On Linux, use 'ldd' on executables or 'ldconfig -p | grep jasper' to find linked libraries. Check application documentation or build configurations.Affected if Applications or services are found that link to libjasper and process image files.
-
Determine if JPEG 2000 processing is enabledIdentify whether any configured application or service processes JPEG 2000 (.jp2, .j2k, .jpx, .jpm) image files. Check application configurations, file processing pipelines, or image handling settings.Affected if JPEG 2000 image processing is actively used or configured in any application using JasPer.
You are affected if JasPer version 1.900.1 is installed AND any application or service on the system processes JPEG 2000 image files using that library.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate JasPer to a patched version (1.900.2 or later). Identify and rebuild all applications and services that link against the JasPer library, then test image processing functionality to verify the fix does not introduce regressions.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-2089 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-2089 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data