dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2011-4517

MEDIUM · 6.8 CVSS v2.0 Published 2011-12-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
The jpc_crg_getparms function in libjasper/jpc/jpc_cs.c in JasPer 1.900.1 uses an incorrect data type during a certain size calculation, which allows remote attackers to trigger a heap-based buffer overflow and execute arbitrary code, or cause a denial of service (heap memory corruption), via a crafted component registration (CRG) marker segment in a JPEG2000 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 confidence

JasPer 1.900.1 contains a heap-based buffer overflow vulnerability in the jpc_crg_getparms function (libjasper/jpc/jpc_cs.c). The flaw stems from using an incorrect data type during size calculation when processing Component Registration (CRG) marker segments in JPEG2000 files. This allows remote attackers to overflow heap buffers and potentially execute arbitrary code or cause heap memory corruption via specially crafted JPEG2000 files.

MitigationUpgrade to a patched version of JasPer that corrects the data type handling in jpc_crg_getparms. If upgrading is not immediately feasible, implement input validation on JPEG2000 files to reject files with malformed CRG marker segments before processing.

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:= 10.04= 10.10= 11.04= 11.10
Debian LinuxOperating system
Affected:= 6.0
FedoraOperating system
Affected:= 15= 16
Enterprise Linux DesktopOperating system
Affected:= 4
JasperApplication
Affected:= 1.900.1
Outside In TechnologyApplication
Affected:= 8.3.5= 8.3.7
Linux Enterprise DesktopOperating system
Affected:= 11
Linux Enterprise ServerOperating system
Affected:= 11

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

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 installed JasPer library version
    On Debian/Ubuntu: dpkg -l | grep jasper or dpkg -s libjasper1. On RHEL/Fedora: rpm -qa | grep jasper. On SUSE: rpm -qa | grep jasper. Or check file /usr/lib/libjasper.so.1 and use 'strings' or check the so version.
    Affected if Version is 1.900.1 exactly
  2. Verify JPEG2000 file processing is occurring
    Identify applications or services that process JPEG2000 (.jp2, .j2k, .jpc) files. Check process list, file type handlers, or application logs for JPEG2000 image operations.
    Affected if JasPer library processes untrusted JPEG2000 files with CRG marker segments
  3. Confirm Oracle Outside In version if used
    If using Oracle Outside In Technology for document conversion, check installed version via Oracle inventory, file version of outsidein libraries, or product documentation.
    Affected if Version equals 8.3.5 or 8.3.7 and processes JPEG2000 input files
  4. Check for vulnerable binary or library presence
    Locate libjasper binaries: find / -name 'libjasper*' 2>/dev/null. Check version strings within the binary using 'strings libjasper.so.1 | grep -i version' or similar.
    Affected if Binary version is 1.900.1 and is being used for JPEG2000 processing

You are affected if you have JasPer version 1.900.1 or Oracle Outside In 8.3.5/8.3.7 installed and process JPEG2000 images through applications using the vulnerable jpc_crg_getparms function.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of JasPer that corrects the data type handling in jpc_crg_getparms. If upgrading is not immediately feasible, implement input validation on JPEG2000 files to reject files with malformed CRG marker segments before processing.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-4517 — 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-2011-4517 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