Ubuntu LinuxOperating system · Canonical
CVE-2016-2116
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 · uneditedMemory leak in the jas_iccprof_createfrombuf function in JasPer 1.900.1 and earlier allows remote attackers to cause a denial of service (memory consumption) via a crafted ICC color profile in a JPEG 2000 image file.
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 confidenceA memory leak exists in the jas_iccprof_createfrombuf function of JasPer 1.900.1 and earlier when parsing ICC color profiles embedded in JPEG 2000 image files. The function fails to properly deallocate memory after creating an ICC profile object, causing memory consumption to grow with each specially crafted image processed.
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
Ubuntu LinuxOperating system
= 12.04= 14.04= 15.10<= 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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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 installedOn Ubuntu, run: dpkg -l | grep -i jasper or check for libjasper.so shared library in /usr/lib/Affected if JasPer library packages are present on the system
-
Determine installed JasPer versionRun: dpkg -l libjasper1 or jasper --version; compare the version number to 1.900.1Affected if The installed version is 1.900.1 or earlier (any version up to and including 1.900.1)
-
Identify applications or services using JasPerCheck for processes or applications that handle JPEG 2000 image formats (JP2, J2K files); common tools include ImageMagick, graphicsmagick, or raw image processors that link against libjasperAffected if Applications that link to the JasPer library are used to process JPEG 2000 format images
-
Detect JPEG 2000 files with embedded ICC profilesExamine JPEG 2000 image files for ICC color profile data using tools like identify (ImageMagick) or hexdump to look for 'icc' profile markers within JP2 filesAffected if JPEG 2000 images being processed contain embedded ICC color profile data
The environment is affected if JasPer version 1.900.1 or earlier is installed AND the system processes JPEG 2000 image files that contain embedded ICC color profiles, causing repeated memory allocation without deallocation.
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 library to version 1.900.2 or later which contains the fix for proper memory management in the jas_iccprof_createfrombuf function.
Fix this in Ubuntu Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-2116 — 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-2116 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