dbcve.org
FedoraOperating system · Fedoraproject

CVE-2017-1000050

HIGH · 7.5 CVSS v3.1 Published 2017-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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
JasPer 2.0.12 is vulnerable to a NULL pointer exception in the function jp2_encode which failed to check to see if the image contained at least one component resulting in a denial-of-service.

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 2.0.12 contains a NULL pointer dereference vulnerability in the jp2_encode function. The function fails to validate that the input image contains at least one component before processing, leading to a NULL pointer dereference when the image data is accessed without this check, causing a denial-of-service condition.

MitigationUpdate JasPer to a version that includes proper validation in jp2_encode, or implement input validation to reject JPEG2000 images lacking component data before passing them to the library.

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
FedoraOperating system
Affected:= 32= 33
Enterprise Linux DesktopOperating system
Affected:= 7.0
Enterprise Linux ServerOperating system
Affected:= 7.0
Enterprise Linux WorkstationOperating system
Affected:= 7.0
Ubuntu LinuxOperating system
Affected:= 14.04= 16.04
JasperApplication
Affected:= 2.0.12

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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

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

  1. Identify JasPer library version
    Run 'rpm -q jasper' on RHEL/Fedora, or 'dpkg -l libjasper*' on Ubuntu, or check via 'jasper --version' if the CLI tool is installed
    Affected if Version equals 2.0.12 exactly, or falls within the affected distribution versions (Fedora 32/33, RHEL 7.0, Ubuntu 14.04/16.04) which ship the vulnerable JasPer 2.0.12 package
  2. Locate the JasPer library file
    Find the shared library with 'find /usr -name "libjasper*" 2>/dev/null' and check its metadata via 'rpm -qf /path/to/libjasper.so' or 'dpkg -S /path/to/libjasper.so'
    Affected if The library package traces back to an affected version listed in the CVE
  3. Identify applications using JasPer for JP2 encoding
    Search for processes or applications that encode JPEG2000 images, such as image converters, viewers, or media processing tools that depend on libjasper. Check with 'ldd /path/to/binary | grep jas' or review application dependencies
    Affected if Applications linked against the vulnerable JasPer library are in use for JP2 encoding operations
  4. Inspect JP2 image processing workflow
    Review any custom code or scripts that call jp2_encode functionality, or audit logs for JPEG2000 encoding activity
    Affected if The jp2_encode function is being invoked to process JP2 images, particularly when handling untrusted input files without prior validation

You are affected if JasPer version 2.0.12 (or the vulnerable packages from affected distributions) is installed AND your environment performs JP2 encoding operations using the jp2_encode function on images that may lack component data.

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 to a version that includes proper validation in jp2_encode, or implement input validation to reject JPEG2000 images lacking component data before passing them to the library.

Fix this in Fedora Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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