CVE-2024-11531
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 · uneditedIrfanView CGM File Parsing Out-Of-Bounds Read 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 read past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-24606.
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 confidenceIrfanView fails to properly validate user-supplied data during CGM (Computer Graphics Metafile) file parsing, leading to an out-of-bounds read operation that reads past the end of an allocated memory buffer. This memory access violation can be leveraged by an attacker to manipulate memory state and achieve arbitrary code execution within the context of the running process.
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= 4.67CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify IrfanView installation existsCheck for IrfanView installation directory (typically C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView) and confirm irfanview.exe is presentAffected if IrfanView is installed on the system
-
Confirm installed version is 4.67Right-click irfanview.exe, select Properties, and check the File Version field, or run 'irfanview.exe /about' via command promptAffected if The version displayed is exactly 4.67 (this specific version is affected)
-
Verify CGM file handling capability is presentCheck the IrfanView plugins folder (usually in the installation directory under 'Plugins') for cgmxdx.dll or similar CGM-related plugin filesAffected if CGM plugin files exist in the Plugins directory, indicating CGM parsing is available
-
Confirm CGM file associations or preview are enabledCheck Windows file associations for .cgm files (via Settings > Apps > Default apps > Choose default apps by file type) or attempt to open a CGM file in IrfanView to see if it rendersAffected if CGM files can be opened or previewed directly within IrfanView
-
Identify if untrusted CGM files may be processedSearch for CGM files in download folders, email attachments, or network shares that could be opened with IrfanViewAffected if User has access to or frequently opens CGM files from untrusted sources using IrfanView
A user is affected if IrfanView version 4.67 is installed AND CGM file handling is enabled, allowing specially crafted CGM files to trigger the out-of-bounds read during parsing.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor patches from IrfanView when available. Until then, avoid opening untrusted or unverified CGM files and consider disabling CGM file preview/handling in the application. Implement file type validation and consider running IrfanView in a sandboxed or isolated environment for untrusted content.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11531 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-11531 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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