dbcve.org
IrfanviewApplication

CVE-2024-11507

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 Type Confusion 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 type confusion condition. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-22177.

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 a type confusion vulnerability in IrfanView's DXF file parser. The parser fails to properly validate user-supplied data during DXF file parsing, allowing an attacker to trigger a type confusion condition that leads to arbitrary code execution in the context of the current process. Exploitation requires a user to open a specially crafted malicious DXF file.

MitigationUsers should avoid opening untrusted or unverified DXF files until a patch is available. Monitor vendor advisories for IrfanView updates addressing this vulnerability.

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

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 is installed
    Check for IrfanView installation by looking for the executable. Common paths: C:\Program Files\IrfanView\i_view64.exe or C:\Program Files (x86)\IrfanView\i_view32.exe. Also check Start Menu or use 'where i_view64.exe' or 'where i_view32.exe' in Command Prompt.
    Affected if IrfanView is not installed on the system - not affected
  2. Determine the installed IrfanView version
    Right-click the IrfanView executable (i_view64.exe or i_view32.exe), select Properties, and check the Details tab for the File Version. Alternatively, open IrfanView and go to Help > About IrfanView to see the exact version number.
    Affected if The version is exactly 4.62 - the system is affected by this specific CVE
  3. Check if DXF file handling is available
    Open IrfanView and attempt to open a DXF file, or check if .dxf files are associated with IrfanView. The DXF parser is a built-in feature for this version.
    Affected if DXF files can be opened or are associated with IrfanView - exploitation is possible if a malicious DXF file is opened
  4. Verify the DXF plugin is present
    Check for the DXF plugin in the IrfanView plugins folder (typically C:\Program Files\IrfanView\Plugins or C:\Program Files (x86)\IrfanView\Plugins). The DXF functionality may be integrated or available as DXF.dll.
    Affected if The DXF parsing capability exists in the plugins folder - the vulnerable code path is present

A system is affected if IrfanView version 4.62 is installed and the DXF file parsing feature is available or enabled, as exploitation requires opening a malicious DXF file with this specific version.

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

Users should avoid opening untrusted or unverified DXF files until a patch is available. Monitor vendor advisories for IrfanView updates addressing this vulnerability.

Fix this in Irfanview Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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