dbcve.org
FormatsApplication · Irfanview

CVE-2024-5875

HIGH · 7.8 CVSS v3.0 Published 2024-11-22
Fix available
A fix is available. Upgrade to after 4.66.2 or later.
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 SHP File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of IrfanView. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of SHP files. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-23972.

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

IrfanView's SHP file parser suffers from an out-of-bounds write vulnerability due to insufficient validation of user-supplied data during parsing. The lack of bounds checking allows an attacker to write data past the end of an allocated buffer, leading to arbitrary code execution in the context of the current process when a user opens a malicious SHP file.

MitigationUsers should avoid opening untrusted SHP files in IrfanView until an official patch is released. Organizations may consider disabling SHP file format support in IrfanView or using alternative image viewers for untrusted files.

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
FormatsApplication
Affected:<= 4.66.2

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.0/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
    Look for IrfanView in the program directory (typically C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView) or check for the application in Add/Remove Programs.
    Affected if IrfanView is not installed on the system.
  2. Identify the IrfanView Formats plugin version
    Navigate to the IrfanView installation directory and locate the Formats plugin file (iformats.dll or similar). Right-click the file, select Properties, and check the Version tab for the product version.
    Affected if The Formats plugin version is 4.66.2 or lower.
  3. Verify SHP file format support exists
    Check the IrfanView plugins folder (usually in the installation directory under a 'plugins' or 'plugins32' subfolder) for a DLL that handles SHP files, or open IrfanView and attempt to view a known SHP file to confirm support is active.
    Affected if SHP format support is present and the version in step 2 is 4.66.2 or lower.
  4. Confirm the exact version number
    In IrfanView, go to Help > About IrfanView or check the version displayed when launching the program. Compare the full version string against the affected range (<= 4.66.2).
    Affected if The displayed version is 4.66.2 or any version lower than 4.66.2.

A user is affected if they have IrfanView with the Formats plugin at version 4.66.2 or lower and the SHP file format support is enabled.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 4.66.2
Interim mitigation

Users should avoid opening untrusted SHP files in IrfanView until an official patch is released. Organizations may consider disabling SHP file format support in IrfanView or using alternative image viewers for untrusted files.

Recommended fix Moderate confidence

IrfanView Formats plugin 4.66.3 or later

  1. 1. Navigate to the official IrfanView website at https://www.irfanview.com/
  2. 2. Download the latest version of IrfanView and the Formats plugin
  3. 3. Uninstall the current IrfanView Formats plugin (version 4.66.2 or lower)
  4. 4. Install the latest IrfanView Formats plugin version (4.66.3 or later)
  5. 5. Verify the installed Formats plugin version by going to Image > Information in IrfanView
  6. 6. Ensure all SHP files are only opened from trusted sources until the update is applied

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Formats Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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