dbcve.org
IrfanviewApplication

CVE-2024-11530

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 CGM 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 CGM 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-24605.

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 CGM (Computer Graphics Metafile) file parser due to insufficient validation of user-supplied data. When processing a maliciously crafted CGM file, the lack of proper bounds checking allows an attacker to corrupt memory, potentially enabling arbitrary code execution within the context of the current process.

MitigationUsers should avoid opening untrusted CGM files and update IrfanView when a vendor patch becomes available. Organizations may consider implementing application whitelisting or endpoint protection to block untrusted file types.

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. Identify the installed IrfanView version
    Open IrfanView, then navigate to Help > About, or right-click the IrfanView executable and select Properties > Details to view the File Version
    Affected if The displayed version is exactly 4.67 (no other versions are listed as affected in this CVE)
  2. Confirm CGM file format support exists
    Check the IrfanView plugins folder (typically 'Plugins' subdirectory in the installation folder) for a CGM-related plugin file such as 'CGM.dll' or check if CGM files can be opened directly in IrfanView
    Affected if CGM file support is present and IrfanView can open .cgm files, meaning the vulnerable parser code is loaded into the process
  3. Inspect recent CGM file access
    Review file access logs, endpoint detection tools, or manually check for recently opened .cgm files in the system to identify potential exploitation attempts
    Affected if Any CGM files have been opened in IrfanView since version 4.67 was installed, indicating the vulnerable code path was exercised

You are affected only if you have IrfanView version 4.67 installed AND CGM file format support is enabled, which allows the malicious CGM parser to be invoked when opening a crafted file.

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

Users should avoid opening untrusted CGM files and update IrfanView when a vendor patch becomes available. Organizations may consider implementing application whitelisting or endpoint protection to block untrusted file types.

Recommended fix Moderate confidence

latest stable IrfanView version (newer than 4.67)

  1. Open IrfanView and navigate to Help > Check for Updates, or visit the official IrfanView website (www.irfanview.com) to download the latest stable version
  2. Download and install the most recent version of IrfanView that addresses the CGM file parsing vulnerability
  3. Verify the installed version by going to Help > About IrfanView
  4. Avoid opening untrusted CGM files until the update is applied
Caveat IrfanView upgrades typically have minimal breaking changes; legacy plugins may need separate updates

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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