CVE-2024-11517
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 JPM 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 JPM 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-24118.
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 · moderate confidenceIrfanView contains an out-of-bounds write vulnerability in its JPM file parser due to insufficient validation of user-supplied data. When parsing a specially crafted JPM file, the application writes past the end of an allocated buffer, allowing an attacker to achieve arbitrary code execution in the context of the current process. Exploitation requires the user to open a malicious JPM file or visit a malicious webpage.
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 installation and versionLocate the IrfanView installation directory (commonly C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView) and check the version information. You can also open IrfanView and navigate to Help > About to view the version, or right-click the IrfanView executable and select Properties > Details.Affected if The installed version is exactly 4.67
-
Confirm the JPM plugin is presentNavigate to the IrfanView plugins folder (usually <install_dir>\plugins\) and search for JPM-related plugin files (typically named jpm.dll or similar).Affected if A JPM plugin file exists in the plugins directory, indicating JPM file support is enabled
-
Check for recent JPM file associationsCheck if .jpm file extension is associated with IrfanView by examining Windows default program settings or checking the file type associations in the Windows Registry under HKCR\.jpmAffected if JPM files are associated with IrfanView, meaning the application can automatically open JPM files
-
Inspect recent file history for JPM accessCheck Windows Recent Items folder or the application's recent files list to see if any JPM files have been opened with IrfanView.Affected if JPM files have been opened using IrfanView, indicating active usage of the vulnerable parser
You are affected if IrfanView version 4.67 is installed AND the JPM plugin is enabled, and users in your environment have opened or may open JPM files with this application.
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 dataDo not open untrusted JPM files with IrfanView. Apply vendor patches or updates to IrfanView once released. Consider disabling or removing the JPM plugin until the patch is applied.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11517 — 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-11517 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