dbcve.org
FlifApplication

CVE-2017-14232

MEDIUM · 5.5 CVSS v3.0 Published 2019-08-15
Fix available
A fix is available. Upgrade to after 2.0.16 or later.
See remediation →
58/100
Remediation priority · Elevated
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
The read_chunk function in flif-dec.cpp in Free Lossless Image Format (FLIF) 0.3 allows remote attackers to cause a denial of service (invalid memory read and application crash) via a crafted flif 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

A denial of service vulnerability exists in the read_chunk function in flif-dec.cpp of FLIF 0.3. The function performs an invalid memory read when parsing a specially crafted FLIF image file, causing the application to crash.

MitigationAvoid opening untrusted or unknown FLIF files. Update to a patched version of FLIF when released by the vendor.

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
FlifApplication
Affected:= 0.3
JasperApplication
Affected:<= 2.0.16

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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. Check installed Flif version
    Run 'flif --version' or 'flif -V' to display the version number
    Affected if The version displayed is exactly 0.3
  2. Check installed Jasper library version
    Run 'jasper --version' or check the library file version (e.g., libjasper.so.X) using 'ldd' or checking package manager
    Affected if The version is 2.0.16 or lower, or the library cannot be identified as a newer release
  3. Identify if Flif processes external FLIF images
    Review any scripts, applications, or services that call the Flif binary or library to decode image files, check for command lines like 'flif input.flif' or programmatic calls to flif-dec functions with external input
    Affected if The application uses Flif 0.3 to decode FLIF images from untrusted or user-supplied sources
  4. Identify if Jasper processes FLIF or similar malformed images
    Review applications using the Jasper library for image decoding, check logs or access patterns for FLIF file processing
    Affected if Jasper <= 2.0.16 is used to decode image files from untrusted sources

You are affected if Flif version 0.3 or Jasper version 2.0.16 or lower is installed and actively used to process FLIF image files from untrusted or external 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 2.0.16
Interim mitigation

Avoid opening untrusted or unknown FLIF files. Update to a patched version of FLIF when released by the vendor.

Fix this in Flif Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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