dbcve.org
IrfanviewApplication

CVE-2024-11539

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

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 contains a memory corruption vulnerability in its DXF file parser due to insufficient validation of user-supplied data. When parsing a specially crafted malicious DXF file, the lack of proper bounds checking leads to memory corruption, which can be leveraged to achieve arbitrary code execution in the context of the current user process.

MitigationOrganizations should deploy vendor patches when available, restrict DXF file handling to trusted sources only, and consider removing or restricting IrfanView's ability to open untrusted DXF files until a patch is applied.

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
    Check if IrfanView is installed by looking for irfanview.exe in common locations such as C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView, or search for the executable using the system search functionality.
    Affected if IrfanView is installed on the system.
  2. Check installed IrfanView version
    Right-click on irfanview.exe, select Properties, and look at the Details tab to find the File Version. Alternatively, open IrfanView and go to Help > About to display the version information.
    Affected if The installed version is exactly 4.67.
  3. Confirm DXF file format support is present
    IrfanView uses plugins for file format support. Check for the presence of plugins\irfanview_plugins.dll or individual format plugins in the IrfanView program directory, and verify that DXF thumbnail handling or viewing capability is available.
    Affected if DXF file format support is enabled or available in IrfanView.
  4. Inspect recent file associations or opened files
    Check Windows recent files, jump lists, or the IrfanView recent files list (if accessible) for any recently opened .dxf files.
    Affected if The user has recently opened untrusted DXF files with IrfanView.

A user is affected if IrfanView version 4.67 is installed with DXF file format support enabled and the user opens or has opened untrusted or malicious DXF files.

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

Organizations should deploy vendor patches when available, restrict DXF file handling to trusted sources only, and consider removing or restricting IrfanView's ability to open untrusted DXF files until a patch is applied.

Recommended fix Moderate confidence

IrfanView 4.68 or later

  1. 1. Visit the official IrfanView website at https://www.irfanview.com/
  2. 2. Navigate to the downloads section
  3. 3. Download the latest version of IrfanView (currently version 4.68 or later)
  4. 4. Uninstall the current version (4.67) from your system
  5. 5. Install the newly downloaded version
  6. 6. Verify the installation by checking Help > About IrfanView shows version 4.68 or later
  7. 7. Test that DXF files open correctly in the updated version
Caveat Minor: Verify any third-party plugins 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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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