CVE-2017-13745
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 · uneditedThere is a reachable assertion abort in the function jpc_dec_process_sot() in jpc/jpc_dec.c in JasPer 2.0.12 that will lead to a remote denial of service attack by triggering an unexpected jpc_ppmstabtostreams return value, a different vulnerability than CVE-2018-9154.
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 reachable assertion abort exists in JasPer 2.0.12's jpc_dec_process_sot() function in jpc/jpc_dec.c. When processing a specially crafted JPEG-2000 file, the function jpc_ppmstabtostreams returns an unexpected value that triggers an assertion failure, causing denial of service.
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= 2.0.12CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Verify JasPer installationRun 'dpkg -l | grep jasper' on Debian-based systems, 'rpm -qa | grep jasper' on RHEL-based systems, or check for libjasper files with 'find /usr -name "libjasper*" 2>/dev/null'Affected if JasPer library is not present on the system, meaning the software is not installed or has been removed
-
Identify JasPer versionRun 'jasper --version' or check the library version with 'strings /usr/lib/x86_64-linux-gnu/libjasper.so.* 2>/dev/null | grep -i "2\.0\.12"'. On RPM systems, use 'rpm -q jasper'Affected if The installed version is exactly 2.0.12, matching the vulnerable version in the affected products list
-
Confirm JPEG-2000 processing capabilityCheck if any application on the system links to libjasper and processes image files. Use 'ldd /path/to/application | grep jas' or check application logs for .jp2, .j2k, .jpc file processingAffected if Applications process JPEG-2000 files and link against the vulnerable JasPer library version 2.0.12
-
Inspect application dependenciesFor web servers or image processing services, review their dependency lists or use 'ldconfig -p | grep jas' to list all JasPer-linked executablesAffected if Any executable loads libjasper and handles untrusted JPEG-2000 input files
The environment is affected only if JasPer version 2.0.12 is installed AND applications process JPEG-2000 files using the vulnerable library component.
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 dataUpgrade to a patched version of JasPer. If upgrade is not immediately feasible, validate and sanitize all JPEG-2000 input files before processing, or disable JPEG-2000 parsing for untrusted content.
- Consultation3.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA3.0 h
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 locallyCheck whether your project pulls in CVE-2017-13745 — 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-2017-13745 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