dbcve.org
IrfanviewApplication

CVE-2024-6821

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 CIN 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 CIN 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-23260.

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 CIN file parsing functionality. The flaw results from insufficient validation of user-supplied data during CIN file processing, allowing a write operation to extend beyond the boundaries of an allocated memory buffer. This can be exploited to achieve arbitrary code execution within the context of the running process.

MitigationUsers should refrain from opening untrusted or unknown CIN files and avoid visiting malicious webpages until an official patch is available from IrfanView.

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.66

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. Check if IrfanView is installed
    Open Windows Start menu, search for 'IrfanView', or check Program Files folder (usually C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView) for irfanview.exe
    Affected if IrfanView executable exists on the system
  2. Identify installed IrfanView version
    Right-click irfanview.exe, select Properties, then click the Details tab to view the File Version
    Affected if The version listed is exactly 4.66
  3. Verify CIN file support is present
    Launch IrfanView, go to menu Options > Plugins. Look for any CIN-related plugin (CIN file type handler) in the Plugins list
    Affected if CIN plugin or CIN file type support is enabled in IrfanView
  4. Confirm vulnerability trigger condition
    The vulnerability is triggered only when opening a specially crafted CIN file. Check recent file history or email attachments for any opened .cin files from untrusted sources
    Affected if A malicious CIN file has been opened with IrfanView version 4.66

You are affected only if IrfanView version 4.66 is installed AND CIN file support is enabled AND an untrusted CIN file has been opened

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 refrain from opening untrusted or unknown CIN files and avoid visiting malicious webpages until an official patch is available from IrfanView.

Recommended fix Moderate confidence

IrfanView 4.70 or latest stable release

  1. Navigate to the official IrfanView website at www.irfanview.com
  2. Locate the Downloads section
  3. Download the latest version of IrfanView (version 4.70 or newer)
  4. Run the installer and follow the prompts to upgrade
  5. Verify the installation completed successfully
Caveat IrfanView minor version upgrades typically have no breaking changes; plugins may need updating to match the new version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Irfanview Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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