dbcve.org
IrfanviewApplication

CVE-2024-6822

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

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 fails to properly validate user-supplied data when parsing CIN ( Cineon ) image files, leading to an out-of-bounds write past the end of an allocated buffer. This can be triggered by convincing a user to open a malicious CIN file, allowing attackers to execute arbitrary code in the context of the current process.

MitigationAvoid opening CIN files from untrusted sources. Apply vendor patches for IrfanView when available. Consider using antivirus scanning on untrusted files before opening.

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 installed IrfanView version
    Open IrfanView and go to Help > About, or right-click the IrfanView executable and view Properties > Details to see the version number
    Affected if The version shown is exactly 4.66
  2. Verify CIN file support exists
    Check if the CIN (Cineon) image format is recognized by IrfanView by attempting to open a known benign CIN file, or look for cin.dll or similar CIN-related plugin files in the IrfanView installation folder
    Affected if CIN file support is present and IrfanView can open CIN images
  3. Review recent file access for CIN files
    Check Windows Event Viewer under Security or use PowerShell 'Get-ItemProperty' on recently accessed CIN files in your user directories to see if any CIN files were opened recently
    Affected if Any CIN files from untrusted sources were opened using IrfanView around the time this CVE became public
  4. Inspect IrfanView process memory
    If IrfanView is currently running or was recently running, use Task Manager or a memory forensics tool to examine the process for unusual behavior or injected code
    Affected if The IrfanView process exhibits unexpected behavior or contains injected code after opening a CIN file

You are affected if you have IrfanView version 4.66 installed and have opened CIN files from untrusted sources, as the vulnerability requires both the vulnerable version and user interaction with a malicious CIN file.

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

Avoid opening CIN files from untrusted sources. Apply vendor patches for IrfanView when available. Consider using antivirus scanning on untrusted files before opening.

Recommended fix Moderate confidence

IrfanView 4.67 or later

  1. 1. Visit the official IrfanView website at https://www.irfanview.com/ to download the latest version
  2. 2. Download the most recent version of IrfanView (version 4.67 or later)
  3. 3. Close any running instances of IrfanView
  4. 4. Run the installer and follow the prompts to upgrade
  5. 5. After upgrading, avoid opening untrusted CIN files from unknown sources
Caveat Minor: Ensure plugins are also updated 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
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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