CVE-2017-15263
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) with PDF plugin version 4.43 allows attackers to cause a denial of service or possibly have unspecified other impact via a crafted .pdf file, related to "Data from Faulting Address controls Branch Selection starting at PDF!xmlListWalk+0x00000000000166c4."
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 confidenceMemory corruption vulnerability in IrfanView PDF plugin allows remote attackers to control branch selection via crafted PDF files, leading to denial of service or potential code execution. The issue affects xmlListWalk function in the PDF plugin.
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.43= 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.
-
Locate IrfanView installationSearch for irfanview.exe in common installation directories (C:\Program Files\IrfanView, C:\Program Files (x86)\IrfanView) or check Start Menu shortcutsAffected if IrfanView executable is found on the system
-
Determine IrfanView versionRight-click irfanview.exe, select Properties, then Details tab to view File Version; or run 'irfanview.exe /?' and look for version informationAffected if Installed version equals 4.44 (the vulnerable version per the affected range)
-
Locate PDF pluginCheck for PDF.dll in the IrfanView plugins folder (typically C:\Program Files\IrfanView\Plugins or similar)Affected if PDF plugin file (PDF.dll) exists in the plugins directory
-
Determine PDF plugin versionRight-click PDF.dll in the plugins folder, select Properties, then Details to view File Version; compare to 4.43Affected if PDF plugin version equals 4.43 (the vulnerable version per the affected range)
-
Verify PDF functionality is accessibleAttempt to open a PDF file with IrfanView or check if PDF files are associated with IrfanViewAffected if PDF files can be opened in IrfanView, meaning the plugin is enabled and loaded
User is affected if both IrfanView version 4.44 and PDF plugin version 4.43 are installed, and the PDF plugin is active (can open PDF 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 PDF plugin to patched versions; avoid opening untrusted PDF files in vulnerable versions; consider using alternative PDF viewers for files from untrusted sources.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15263 — 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-15263 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