dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2016-1577

HIGH · 7.6 CVSS v3.0 Published 2016-04-13
Fix available
A fix is available. Upgrade to after 1.900.1 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Double free vulnerability in the jas_iccattrval_destroy function in JasPer 1.900.1 and earlier allows remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via a crafted ICC color profile in a JPEG 2000 image file, a different vulnerability than CVE-2014-8137.

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 confidence

Double free vulnerability in the jas_iccattrval_destroy function in JasPer 1.900.1 and earlier allows remote attackers to cause a denial of service or potentially execute arbitrary code via a crafted ICC color profile embedded in a JPEG 2000 image file.

MitigationUpgrade JasPer to a version newer than 1.900.1 that addresses this vulnerability. If upgrading is not immediately feasible, consider input validation or sandboxing for JPEG 2000 files from untrusted sources until the patch can be applied.

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
Affected:= 12.04= 14.04= 15.10
JasperApplication
Affected:<= 1.900.1

CVSS 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
Low
Integrity
Low
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if JasPer is installed
    Run 'dpkg -l | grep jasper' on Debian/Ubuntu systems, or 'rpm -qa | grep jasper' on RHEL-based systems. On other systems, check for the presence of libjasper libraries (typically libjasper.so or jasper binaries).
    Affected if JasPer is installed on the system
  2. Determine the installed JasPer version
    Run 'jasper --version' or 'dpkg -s libjasper1' on Ubuntu. Check the library version with 'pkg-config --modversion jasper' or inspect the shared library file directly with 'dpkg -L libjasper1 | grep so' to find the actual file, then run 'strings' or check file properties.
    Affected if The version is 1.900.1 or earlier, or the version cannot be determined and JasPer is present on affected Ubuntu versions (12.04, 14.04, 15.10)
  3. Identify applications or services using JasPer
    Search for binaries or libraries linked against libjasper using 'ldd <binary>' on suspected image processing tools, or check for packages that depend on libjasper with 'apt-cache rdepends libjasper1' on Ubuntu.
    Affected if Applications that process JPEG 2000 images using JasPer are in use
  4. Check for JPEG 2000 image processing workflows
    Review any image processing pipelines, file upload handlers, or services that accept image uploads and could contain JPEG 2000 files (.jp2 extension). Check configuration files for image processing libraries that may invoke JasPer.
    Affected if The system processes or serves JPEG 2000 images from untrusted sources
  5. Verify ICC profile handling in JPEG 2000 processing
    Examine if any image processing code or tools explicitly handle ICC color profiles within JPEG 2000 files. Look for tools like 'identify' from ImageMagick or other image utilities that may invoke the vulnerable jas_iccattrval_destroy code path.
    Affected if JPEG 2000 images with embedded ICC profiles are being processed

A user is affected if JasPer version 1.900.1 or earlier is installed and the system processes JPEG 2000 images containing ICC color profiles from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.900.1
Interim mitigation

Upgrade JasPer to a version newer than 1.900.1 that addresses this vulnerability. If upgrading is not immediately feasible, consider input validation or sandboxing for JPEG 2000 files from untrusted sources until the patch can be applied.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1577 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-1577 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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