IrfanviewApplication

CVE-2024-11520

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 ARW 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 ARW 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 object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-24488.

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

An out-of-bounds write vulnerability exists in IrfanView's ARW (Sony RAW image) file parsing functionality. The vulnerability results from insufficient validation of user-supplied data during file parsing, allowing a write operation to extend beyond the boundaries of an allocated memory object. This can be triggered by convincing a user to open a specially crafted malicious ARW file, leading to arbitrary code execution in the context of the current process.

MitigationAvoid opening untrusted or unexpected ARW files in IrfanView until an official vendor patch is available. Consider disabling or restricting file type associations for ARW files in untrusted contexts, and ensure antivirus scanning is enabled for file attachments.

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

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. Verify IrfanView installation and version
    Locate IrfanView on the system - common paths include C:\Program Files\IrfanView\i_view32.exe or C:\Program Files (x86)\IrfanView\i_view32.exe. Right-click the executable, select Properties, and check the File Version field under the Details tab. Alternatively, launch IrfanView and go to Help > About IrfanView to display the version number.
    Affected if The installed version is exactly 4.67
  2. Confirm ARW file type support is active
    Check if IrfanView can open ARW files by attempting to open a sample .arw file, or by examining File > Open dialog and looking for 'Sony RAW Format (*.arw)' in the file type dropdown. Also check File > Options > File associations to see if ARW is listed as an associated extension.
    Affected if ARW files are listed as an associated file type and IrfanView can open them
  3. Determine if ARW files are handled by IrfanView
    Check Windows file type associations for .arw extension by going to Control Panel > Default Programs > Set Associations, or by inspecting the registry under HKEY_CLASSES_ROOT\.arw to see if IrfanView is set as the handler. Also check if any applications use IrfanView as a thumbnail generator for ARW files.
    Affected if The .arw file extension is associated with IrfanView or IrfanView is configured to handle ARW files as a thumbnail/preview handler

A user is affected if IrfanView version 4.67 is installed AND the ARW file type is associated with or can be opened by IrfanView.

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

Avoid opening untrusted or unexpected ARW files in IrfanView until an official vendor patch is available. Consider disabling or restricting file type associations for ARW files in untrusted contexts, and ensure antivirus scanning is enabled for file attachments.

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-2024-11520 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-11520 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