dbcve.org
IrfanviewApplication

CVE-2024-11564

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 DWG 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 DWG 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-24864.

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 DWG file parsing functionality. The lack of proper validation of user-supplied data during DWG file parsing allows an attacker to trigger memory corruption, potentially leading to arbitrary code execution in the context of the current process. Exploitation requires user interaction such as opening a malicious DWG file.

MitigationAvoid opening untrusted or unverified DWG files in IrfanView. Monitor for and apply vendor security patches or updates to IrfanView as they become available. Consider using alternative DWG viewers or disabling DWG plugin support in IrfanView as a temporary workaround if the vendor patch is delayed.

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. Check installed IrfanView version
    Open IrfanView and go to Help > About, or right-click the IrfanView executable and select Properties to view the version number
    Affected if The installed version is exactly 4.67
  2. Verify DWG plugin is present
    Check the IrfanView plugins folder (typically C:\Program Files\IrfanView\Plugins or C:\Program Files (x86)\IrfanView\Plugins) for the DWG file (such as DWG.dll or similar DWG-related plugin)
    Affected if A DWG parsing plugin file exists in the Plugins folder
  3. Confirm DWG file association or capability
    Attempt to open a DWG file in IrfanView or check if .dwg appears in the list of supported file types in IrfanView's options or if DWG files are directly openable
    Affected if IrfanView can open or recognizes DWG files

A user is affected if they have IrfanView version 4.67 installed AND have the DWG plugin or DWG file handling capability enabled, making them vulnerable when opening malicious DWG 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

Avoid opening untrusted or unverified DWG files in IrfanView. Monitor for and apply vendor security patches or updates to IrfanView as they become available. Consider using alternative DWG viewers or disabling DWG plugin support in IrfanView as a temporary workaround if the vendor patch is delayed.

Recommended fix Moderate confidence

IrfanView latest stable version (newer than 4.67)

  1. 1. Visit the official IrfanView website (www.irfanview.com) to check for the latest version.
  2. 2. Download and install the most recent stable version of IrfanView.
  3. 3. Verify the installed version matches or exceeds the fixed release.
  4. 4. Ensure all IrfanView plugins are also updated to their latest versions, as plugins may contain the vulnerable DWG parsing code.

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

Fix this in Irfanview Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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