dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2011-4516

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
Heap-based buffer overflow in the jpc_cox_getcompparms function in libjasper/jpc/jpc_cs.c in JasPer 1.900.1 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted numrlvls value in a coding style default (COD) 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

Heap-based buffer overflow in the jpc_cox_getcompparms function in libjasper/jpc/jpc_cs.c of JasPer 1.900.1 allows remote code execution or DoS via a crafted numrlvls value in a JPEG2000 file's COD marker segment, causing memory corruption.

MitigationUpdate JasPer library to a patched version. If update unavailable, validate and sanitize JPEG2000 input files before processing, or restrict processing to trusted files only.

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
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
Linux Enterprise Software Development KitOperating 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. Check if JasPer library is installed
    On Debian/Ubuntu: dpkg -l | grep libjasper. On Fedora/RHEL: rpm -qa | grep jasper. On SUSE: rpm -qa | grep jasper.
    Affected if libjasper package is found on the system
  2. Identify the installed JasPer version
    Run: dpkg -l libjasper1 (Debian/Ubuntu) or rpm -q libjasper (Fedora) or rpm -q libjasper (SUSE). Compare the version number to 1.900.1.
    Affected if Installed version is 1.900.1 exactly, or falls within the 1.900.1 release line
  3. Check for JasPer development files or linked binaries
    Search for binaries or applications linked against libjasper: ldd /path/to/application | grep jasper, or locate jasper-related shared objects in /usr/lib or /usr/lib64.
    Affected if Applications using libjasper are present on the system
  4. Determine if JPEG2000 file processing is enabled
    Identify applications that process image files (e.g., image viewers, document converters, graphics tools) and check if they can load .jp2, .j2k, .jpc, or .jpx files. Test by attempting to load a JPEG2000 file or reviewing application file type support.
    Affected if Applications can process JPEG2000 file formats using JasPer library
  5. Verify if untrusted JPEG2000 input is processed
    Review log files, web upload directories, document processing workflows, or email attachments that may contain JPEG2000 images. Check if any service accepts and processes .jp2 files from external sources.
    Affected if The system processes JPEG2000 files from untrusted or external sources

The system is affected if JasPer library version 1.900.1 is installed and the system or any application uses it to process JPEG2000 files from any source.

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

Update JasPer library to a patched version. If update unavailable, validate and sanitize JPEG2000 input files before processing, or restrict processing to trusted files only.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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