dbcve.org
IrfanviewApplication

CVE-2019-17255

HIGH · 7.8 CVSS v3.1 Published 2019-10-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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
IrfanView 4.53 allows a User Mode Write AV starting at EXR!ReadEXR+0x0000000000010836.

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 · moderate confidence

Memory corruption vulnerability in IrfanView 4.53's EXR image file parser (ReadEXR function). A specially crafted EXR file triggers a User Mode Write Access Violation, allowing an attacker to write arbitrary memory values and potentially achieve code execution.

MitigationUpgrade to a patched version of IrfanView that addresses this vulnerability; avoid opening untrusted EXR files until the update is applied.

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
IrfanviewApplication
Affected:= 4.53

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
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 checks

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

  1. Check if IrfanView is installed
    Locate IrfanView installation directory (typically C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView) and look for i_view32.exe or i_view64.exe
    Affected if IrfanView executable exists on the system
  2. Identify installed IrfanView version
    Right-click the IrfanView executable (i_view32.exe or i_view64.exe), select Properties, and check the File Version in the Details tab. Alternatively, open IrfanView and go to Help > About
    Affected if Version displayed is exactly 4.53
  3. Verify EXR plugin is present
    Check the IrfanView plugins folder (usually C:\Program Files\IrfanView\Plugins or within the installation directory) for exr.dll or similar EXR-related plugin files
    Affected if EXR plugin file exists in the plugins directory
  4. Confirm EXR file handling is possible
    Attempt to open a sample .exr file in IrfanView, or verify IrfanView is associated with .exr file extension
    Affected if IrfanView can load and process EXR image files

User is affected if IrfanView version 4.53 is installed and EXR file format support (via plugin or built-in) is available on the system

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

Upgrade to a patched version of IrfanView that addresses this vulnerability; avoid opening untrusted EXR files until the update is applied.

Fix this in Irfanview Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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 locally
dbcve dependency scanner

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