CVE-2019-17253
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 a User Mode Write AV starting at JPEG_LS+0x000000000000a6b8.
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 · low confidenceIrfanView 4.53 contains a User Mode Write Access Violation vulnerability in its JPEG_LS image parsing component at offset 0xa6b8. This memory corruption issue can be triggered by a specially crafted JPEG_LS image file, potentially allowing an attacker to achieve code execution if they can control the memory write primitive.
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.
-
Check if IrfanView is installedLook for IrfanView in Program Files (typically C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView) or check the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\IrfanView or HKEY_CURRENT_USER\SOFTWARE\IrfanViewAffected if IrfanView is installed on the system
-
Determine the installed IrfanView versionRight-click irfanview.exe, select Properties, then look at the Details tab for the File Version, or run irfanview.exe /? and check the version information displayedAffected if The version is exactly 4.53 (other versions are not affected by this CVE)
-
Verify JPEG_LS file handling capabilityCheck the IrfanView plugins folder (typically C:\Program Files\IrfanView\plugins) for JPEG_LS related plugins, and confirm IrfanView is configured to handle .jls or other JPEG_LS file extensionsAffected if JPEG_LS support is present and the user opens a specially crafted JPEG_LS image file
The environment is affected only if IrfanView version 4.53 is installed and a user opens a malicious JPEG_LS image file with that version.
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 IrfanView newer than 4.53, or avoid opening untrusted JPEG_LS image files in the affected version.
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17253 — 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-17253 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