CVE-2019-17247
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 · uneditedIrfanView 4.53 allows Data from a Faulting Address to control a subsequent Write Address starting at JPEG_LS+0x0000000000007da8.
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 confidenceIrfanView 4.53 contains a memory corruption vulnerability in its JPEG-LS image parsing component. The vulnerability allows data from a faulting address to control a subsequent write address (at JPEG_LS+0x7da8), potentially enabling arbitrary code execution via a specially crafted malicious JPEG-LS image file.
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= 4.53CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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.
-
Confirm IrfanView installation and locate the executableCheck for IrfanView installation directory (typically C:\Program Files\IrfanView\i_view32.exe or C:\Program Files (x86)\IrfanView\i_view32.exe)Affected if IrfanView is installed and the executable exists
-
Determine installed IrfanView versionRight-click i_view32.exe, select Properties, and check the Version tab for the Product Version field; or run 'i_view32.exe' and go to Help > About IrfanViewAffected if Version displayed is 4.53 exactly
-
Verify JPEG-LS parsing capability is presentCheck the IrfanView Plugins folder (usually in the IrfanView directory under 'Plugins' or 'i_plugins') for JPEG-LS related plugin files (look for files containing 'jpeg' or 'jpg' in filename within the Plugins directory)Affected if JPEG-LS plugin or image handling capability is present in the Plugins directory
-
Confirm vulnerability applicabilityReview version: if the installed version is exactly 4.53 and the application can open or preview JPEG-LS images (via built-in support or plugin), the environment is potentially affectedAffected if Running version 4.53 with JPEG-LS image parsing enabled
You are affected if IrfanView version 4.53 is installed and the JPEG-LS image parsing component is active, as this specific version contains the memory corruption flaw in its JPEG-LS handling code.
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 the latest IrfanView version that includes the vendor security patch for this vulnerability; avoid opening untrusted JPEG-LS image files until patched.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17247 — 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-2019-17247 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