CVE-2024-31007
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 · uneditedBuffer Overflow vulnerability in IrfanView 32bit v.4.66 allows a local attacker to cause a denial of service via a crafted file. Affected component is IrfanView 32bit 4.66 with plugin formats.dll.
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 confidenceA buffer overflow vulnerability exists in IrfanView 32-bit version 4.66 within the formats.dll plugin. When parsing a specially crafted image file, the plugin fails to properly validate buffer boundaries, allowing an attacker to overwrite memory and cause a denial of service (application crash).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 is the 32-bit versionOpen Task Manager, find the IrfanView process (if running), right-click and select Properties. Look at the Image or check if the installed path contains 'Program Files (x86)' which indicates 32-bit software.Affected if The installed IrfanView is the 32-bit variant (found in Program Files x86). The CVE specifically affects 32-bit versions only.
-
Check IrfanView installed versionOpen IrfanView, go to Help > About IrfanView. Alternatively, right-click the IrfanView executable in its install directory, select Properties, and check the File Version field.Affected if The installed version is exactly 4.66. Versions before or after may have different vulnerability status.
-
Locate and verify formats.dll plugin versionNavigate to the IrfanView plugins folder (typically C:\Program Files\IrfanView\Plugins or C:\Program Files (x86)\IrfanView\Plugins), locate formats.dll, right-click and check the File Version in Properties.Affected if The formats.dll plugin version corresponds to IrfanView 4.66. This is the specific component with the buffer overflow vulnerability.
-
Determine if untrusted image files are processedReview your workflows or search the file system for image files from untrusted or unknown sources. Check recent IrfanView 'Recent Files' or default save locations for foreign image files.Affected if Users routinely open image files from untrusted or unknown sources using IrfanView, as the vulnerability is triggered when parsing specially crafted images.
A user is affected if they are running the 32-bit version of IrfanView 4.66 with the formats.dll plugin and open untrusted or specially crafted image 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.
From vendor dataUpdate IrfanView and its plugins to the latest versions, as patches for the formats.dll plugin should address the boundary validation issue. Avoid opening untrusted image files from unknown sources.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31007 — 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-31007 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