IrfanviewApplication

CVE-2024-11548

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 Out-Of-Bounds Write 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 write 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-24745.

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 an out-of-bounds write vulnerability in its DWG file parsing functionality. The flaw results from insufficient validation of user-supplied data during DWG file parsing, allowing writes beyond allocated buffer boundaries. Successful exploitation enables arbitrary code execution within the context of the current process.

MitigationUsers should avoid opening untrusted or unverified DWG files and ensure IrfanView is updated to any available patched version. Organizations may consider disabling DWG file preview or implementing file type restrictions until a patch is applied.

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. Locate IrfanView installation
    Search for i_view64.exe or i_view32.exe in common installation paths such as C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView. Alternatively, open Add or Remove Programs and confirm IrfanView is listed.
    Affected if IrfanView is present on the system
  2. Identify installed version
    Right-click the IrfanView executable (i_view64.exe or i_view32.exe), select Properties, and view the File Version on the Details tab. Alternatively, launch IrfanView and navigate to Help > About to see the version number.
    Affected if The installed version is exactly 4.67
  3. Determine if DWG handling is active
    Check whether IrfanView can open or preview DWG files. Attempt to open a DWG file with IrfanView, or verify if DWG file thumbnails are generated when IrfanView is registered as the thumbnail handler in Windows Explorer.
    Affected if DWG files can be opened, previewed, or thumbnails are generated by IrfanView
  4. Verify DWG plugin presence
    Open the IrfanView plugins folder (typically C:\Program Files\IrfanView\Plugins) and search for any DWG-related DLL files such as dwg.dll or files containing 'dwg' in the name.
    Affected if DWG support plugins are installed and loaded by IrfanView

The environment is affected if IrfanView version 4.67 is installed with DWG file handling capabilities enabled or available plugins present.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Users should avoid opening untrusted or unverified DWG files and ensure IrfanView is updated to any available patched version. Organizations may consider disabling DWG file preview or implementing file type restrictions until a patch is applied.

Fix this in Irfanview Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-11548 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