CVE-2024-11529
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 DWG 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 DWG 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-24604.
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 an out-of-bounds read vulnerability in its DWG file parser due to insufficient validation of user-supplied data. This allows reading past the end of an allocated buffer, which can be leveraged by an attacker to execute arbitrary code in the context of the current process when a user opens a malicious DWG 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.
-
Confirm IrfanView installationCheck for IrfanView in program directories or use system search to locate irfanview.exeAffected if IrfanView is not installed on the system
-
Identify installed versionRight-click irfanview.exe, select Properties, and view the Version tab to determine the exact version numberAffected if The installed version is 4.67
-
Verify DWG plugin availabilityLocate the plugins directory (typically named 'Plugins' in the IrfanView installation folder) and check for DWG-related files such as DWG.dll or iwdsgdsg.dllAffected if DWG support plugins are present in the Plugins folder
-
Check for recent DWG file accessReview recent file history or prefetch data for .dwg file openings through IrfanViewAffected if Users have opened DWG files using IrfanView recently
The environment is affected if IrfanView version 4.67 is installed with DWG file handling capabilities enabled and users have opened or may open DWG files.
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.
dbcve · scopedAvoid opening untrusted DWG files and apply vendor patches when available; consider disabling DWG preview or adding file-type restrictions in enterprise environments until the official fix is released.
Latest stable IrfanView version available on irfanview.com (check version history for post-4.67 release)
- 1. Navigate to the official IrfanView website at https://www.irfanview.com/
- 2. Download the latest version of IrfanView (check the main download page for the most recent release)
- 3. Uninstall the current version (4.67) from your system
- 4. Install the newly downloaded latest version
- 5. Verify the installation was successful by checking Help > About IrfanView
- 6. Ensure all IrfanView plugins are also updated to their latest versions from the plugins download section
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11529 — 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-11529 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