CVE-2017-10730
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+0x0000000000007d96."
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 memory corruption vulnerability exists in IrfanView 4.44 (32-bit) when parsing malformed RLE image files. The vulnerability is triggered in the FORMATS plugin's GetPlugInInfo function during RLE file processing, causing a User Mode Write Access Violation that can be leveraged for arbitrary code execution or 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.
-
Verify IrfanView installationCheck for IrfanView executable (irfanview.exe) in common installation directories such as C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView, or search for the executable on the system.Affected if IrfanView is found on the system.
-
Determine installed IrfanView versionRight-click on irfanview.exe, select Properties, and check the Details tab for the File Version. Alternatively, run 'irfanview.exe /?' at command line to display version information.Affected if The displayed version is exactly 4.44.
-
Confirm 32-bit architectureCheck if the installed IrfanView executable is the 32-bit version. This can be verified by examining the file properties under the Details tab for 'File description' containing '32-bit' or by checking the file location under Program Files (x86) folder.Affected if The installed version is the 32-bit (x86) edition of IrfanView 4.44.
-
Locate the FORMATS pluginCheck for formats.dll plugin in the IrfanView plugins folder (typically C:\Program Files\IrfanView\plugins or C:\Program Files (x86)\IrfanView\plugins).Affected if The FORMATS plugin (formats.dll) exists in the plugins directory.
A system is affected if IrfanView version 4.44 32-bit is installed with the FORMATS plugin present, allowing processing of RLE image files that could trigger the memory corruption vulnerability.
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 dataAvoid opening untrusted or crafted .rle files in IrfanView. Update to a patched version of IrfanView if available, or implement endpoint protection that scans files before opening.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10730 — 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-10730 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