dbcve.org
IrfanviewApplication

CVE-2024-6818

HIGH · 7.8 CVSS v3.1 Published 2024-11-22
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 PSP 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 PSP 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-23217.

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

This is an out-of-bounds write vulnerability in IrfanView's PSP file parser. The lack of proper validation of user-supplied data during PSP (Paint Shop Pro) file parsing allows writing past the end of an allocated buffer, enabling remote code execution in the context of the current process when a user opens a malicious PSP file.

MitigationAvoid opening untrusted PSP files until a vendor patch is available. Monitor IrfanView's official channels for security updates.

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.66

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. Confirm IrfanView installation
    Check for IrfanView installation by looking for 'IrfanView' in Program Files or Program Files (x86), or run 'where i_view64.exe' or 'where i_view32.exe' in Command Prompt
    Affected if IrfanView is installed on the system
  2. Identify installed IrfanView version
    Right-click the IrfanView executable (i_view64.exe or i_view32.exe), select Properties, and check the Version tab for the product version
    Affected if The version is exactly 4.66
  3. Verify PSP file format support exists
    Check if the PSP file type is recognized by opening IrfanView and attempting to browse to a .psp file, or check for PSP-related DLLs in the IrfanView plugins folder (typically 'C:\Program Files\IrfanView\Plugins')
    Affected if PSP files can be opened or PSP-related plugin files are present in the Plugins folder
  4. Check for recent PSP file opening activity
    Review Windows Event Viewer under Security or Application logs for recent IrfanView process events, or check browser/download folders for recently accessed .psp files
    Affected if A user has recently opened a PSP file using IrfanView

The system is affected if IrfanView version 4.66 is installed, the PSP file parser plugin is present, and a user has opened or could open a malicious PSP file.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Avoid opening untrusted PSP files until a vendor patch is available. Monitor IrfanView's official channels for security updates.

Recommended fix Moderate confidence

IrfanView 4.68 or later

  1. 1. Navigate to the official IrfanView website at https://www.irfanview.com/
  2. 2. Download the latest version of IrfanView (version 4.68 or later)
  3. 3. Uninstall the current version (4.66) from your system
  4. 4. Install the newly downloaded version
  5. 5. Verify the installation was successful by checking the version number in Help > About IrfanView
  6. 6. Test that PSP files open correctly in the updated version
Caveat Standard upgrade - ensure any plugins you use are compatible with the new version

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

Fix this in Irfanview Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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