dbcve.org
IrfanviewApplication

CVE-2024-11560

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 DXF File Parsing Memory Corruption 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 DXF files. The issue results from the lack of proper validation of user-supplied data, which can result in a memory corruption condition. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-24853.

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 fails to properly validate user-supplied data when parsing DXF (Drawing Exchange Format) files. This lack of validation leads to memory corruption during the parsing process, allowing an attacker to overwrite memory and execute arbitrary code within the context of the running process. User interaction is required (opening a malicious DXF file).

MitigationDo not open untrusted DXF files with IrfanView. Await the vendor patch from IrfanView. Consider restricting file type associations or using application sandboxing as a defense-in-depth measure until the patch 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.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. Confirm IrfanView is installed
    Check for IrfanView installation in typical locations: C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView, or look for IrfanView in the Windows Start Menu.
    Affected if IrfanView software is present on the system.
  2. Identify installed IrfanView version
    Locate the IrfanView executable (i_view64.exe or i_view32.exe), right-click and select Properties, then check the Details tab for the File Version. Alternatively, open IrfanView and go to Help > About IrfanView to view the version number.
    Affected if The installed version is exactly 4.67.
  3. Verify DXF plugin availability
    Check the IrfanView plugins folder (typically C:\Program Files\IrfanView\Plugins or C:\Program Files (x86)\IrfanView\Plugins) for DXF-related plugins. IrfanView uses external plugins to handle various file formats including DXF.
    Affected if DXF handling capability is present through installed plugins.
  4. Review file type associations
    Check Windows registry under HKEY_CLASSES_ROOT for .dxf file associations, or check IrfanView's own configuration via Options > File Types to see which file types are configured to open with IrfanView.
    Affected if DXF file types are associated with IrfanView or configured to open automatically.

You are affected if IrfanView version 4.67 is installed and DXF file parsing capability (via plugins or built-in support) is enabled on your 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

Do not open untrusted DXF files with IrfanView. Await the vendor patch from IrfanView. Consider restricting file type associations or using application sandboxing as a defense-in-depth measure until the patch is available.

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-11560 — 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-11560 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