CVE-2024-11543
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 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-24704.
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 contains a memory corruption vulnerability in its DXF file parser due to insufficient validation of user-supplied data. When parsing a maliciously crafted DXF file, the lack of proper bounds checking or input validation leads to memory corruption, which can be leveraged by an attacker to achieve arbitrary code execution within the context of the running process. Exploitation requires user interaction in the form of opening a malicious DXF file.
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 installationSearch for irfanview.exe in common installation directories (C:\Program Files\IrfanView, C:\Program Files (x86)\IrfanView) or check Start Menu shortcutsAffected if IrfanView is installed on the system
-
Check installed versionRight-click irfanview.exe, select Properties, and look at the File Version in the Details tab. Alternatively, run 'irfanview.exe' with /? or /version flagAffected if The version shown is exactly 4.67
-
Verify DXF file handling capabilityCheck if i_view32.ini or i_view64.ini exists in the application data folder (%APPDATA%\IrfanView) and look for DXF-related entries, or verify the DXF plugin (Plugins\FileLoader\Plugins.ini) contains DXF supportAffected if DXF file handling is enabled or the DXF plugin is present and loaded
-
Inspect recent file associationsCheck Windows registry under HKCR\.dxf or examine recently opened files in IrfanView's history (check the [RecentFiles] section in i_view32.ini/i_view64.ini)Affected if DXF files are associated with IrfanView or appear in recent file history
If IrfanView version 4.67 is installed with DXF file handling capability enabled and a user opens a malicious DXF file, the memory corruption vulnerability is triggered.
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 dataAvoid opening DXF files from untrusted or unknown sources. Monitor for vendor patches from IrfanView that address input validation in the DXF parser and apply them promptly.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11543 — 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-11543 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