CVE-2017-10731
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 version 4.44 (32bit) allows attackers to execute arbitrary code or cause a denial of service via a crafted .rle file, related to a "User Mode Write AV starting at FORMATS!GetPlugInInfo+0x0000000000007d80."
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 confidenceIrfanView 4.44 (32-bit) contains a buffer overflow in its RLE image format plugin. When processing a specially crafted .rle file, the GetPlugInInfo function attempts to write to invalid memory, causing an access violation that can be leveraged for arbitrary code execution or used to cause a denial of service.
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.44CVSS 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.0/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.
-
Confirm IrfanView is installedCheck for IrfanView installation directory (typically C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView) or search for irfanview.exe on the systemAffected if IrfanView is not installed on the system
-
Identify the installed versionRight-click irfanview.exe, select Properties, then view the Details tab to see the File Version, or run 'irfanview.exe' with /? and check the version string displayedAffected if The installed version is exactly 4.44
-
Determine the architecture (32-bit vs 64-bit)Check the installation path: if installed under C:\Program Files (x86)\IrfanView it is 32-bit; if under C:\Program Files\IrfanView it is 64-bit, or view the file properties to confirm the Binary architectureAffected if The version is 32-bit (x86) architecture
-
Verify the RLE plugin existsCheck for the RLE plugin file (plugins\rle.dll or similar) in the IrfanView installation directory under the plugins folderAffected if The RLE plugin file is present in the plugins directory
The environment is affected only if IrfanView version 4.44 (32-bit) with the RLE plugin is installed; other versions or 64-bit installations are not vulnerable to this specific CVE.
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 to the latest version which contains patched plugins. Until then, avoid opening untrusted .rle files from unknown sources, as the vulnerability can be triggered simply by viewing a malicious image file.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10731 — 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-2017-10731 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