dbcve.org
IrfanviewApplication

CVE-2024-6817

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

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

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 file parsing allows an attacker to write past the end of an allocated buffer, leading to arbitrary code execution in the context of the current process. Exploitation requires user interaction to open a malicious PSP file.

MitigationAvoid opening PSP files from untrusted sources. Apply vendor patches when released. Consider using alternative image viewers or disabling PSP file handling in IrfanView until a fix is available.

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 executable at typical install locations: C:\Program Files\IrfanView\i_view64.exe or C:\Program Files (x86)\IrfanView\i_view32.exe. Also check Start Menu or registry under HKEY_LOCAL_MACHINE\SOFTWARE\IrfanView or HKEY_CURRENT_USER\SOFTWARE\IrfanView.
    Affected if IrfanView is installed on the system
  2. Identify installed version
    Run i_view64.exe --version or i_view32.exe --version from command line, or check the version property of the executable file, or look in registry key HKEY_LOCAL_MACHINE\SOFTWARE\IrfanView\InstallDir for the path and then check the version there.
    Affected if Version is 4.66 exactly or falls within the affected range (if vendor clarifies version range)
  3. Verify PSP plugin is present
    Check the IrfanView plugins folder (typically C:\Program Files\IrfanView\Plugins or C:\Program Files (x86)\IrfanView\Plugins) for PSP-related files such as PSP.dll or formats\PSP.dll.
    Affected if The PSP plugin DLL exists in the plugins folder, meaning PSP file handling is available
  4. Check if PSP file association exists
    Right-click any .psp file in Windows Explorer, select Properties, then open with IrfanView, or check registry HKEY_CLASSES_ROOT\.psp to see if IrfanView is associated with PSP files.
    Affected if IrfanView is set as the default handler for PSP files or has been used to open PSP files previously

User is affected if IrfanView version 4.66 is installed and the PSP plugin is present, as the vulnerability triggers when parsing 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 PSP files from untrusted sources. Apply vendor patches when released. Consider using alternative image viewers or disabling PSP file handling in IrfanView until a fix is available.

Recommended fix Moderate confidence

Latest IrfanView version (check irfanview.com for current release)

  1. 1. Visit the official IrfanView website at https://www.irfanview.com/ to check for the latest version.
  2. 2. Download the most recent version of IrfanView available.
  3. 3. Uninstall the current version (4.66) from your system.
  4. 4. Install the newly downloaded version.
  5. 5. Verify the installed version matches the latest release.
  6. 6. Avoid opening PSP files from untrusted sources until the update is applied.

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

Fix this in Irfanview Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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