IrfanviewApplication

CVE-2017-15248

HIGH · 7.8 CVSS v3.0 Published 2017-10-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
IrfanView version 4.44 (32bit) with PDF plugin version 4.43 allows attackers to execute arbitrary code or cause a denial of service via a crafted .pdf file, related to "Data from Faulting Address controls Code Flow starting at PDF!xmlGetGlobalState+0x0000000000063ca6."

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 confidence

IrfanView 4.44 (32-bit) with PDF plugin 4.43 contains a memory corruption vulnerability where a crafted PDF file triggers a control flow hijack at PDF!xmlGetGlobalState, allowing arbitrary code execution or denial of service.

MitigationUpdate IrfanView and the PDF plugin to vendor-patched versions that resolve this vulnerability.

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
IrfanviewApplication
Affected:= 4.44
PdfApplication
Affected:= 4.43

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check IrfanView executable version
    Open File Explorer, navigate to the IrfanView installation directory (commonly C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView), right-click on i_view32.exe (the 32-bit executable), select Properties, and view the version number on the Details tab
    Affected if The version shown is 4.44 exactly
  2. Check PDF plugin version
    In the IrfanView installation directory, locate the PDF plugin file (commonly named PDF.dll or PDF.x86). Right-click on the file, select Properties, and check the version number on the Details tab
    Affected if The PDF plugin version is 4.43
  3. Verify 32-bit IrfanView is in use
    Confirm that i_view32.exe exists and is the primary executable being used (rather than i_view64.exe for 64-bit)
    Affected if The i_view32.exe (32-bit) executable is being used to run IrfanView with the vulnerable PDF plugin
  4. Confirm PDF plugin is installed
    Check the IrfanView installation directory for the presence of PDF plugin files (PDF.dll or similar)
    Affected if The PDF plugin DLL file is present in the IrfanView installation folder

A user is affected if they are running IrfanView version 4.44 (32-bit) with PDF plugin version 4.43 specifically, as this is the exact vulnerable configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update IrfanView and the PDF plugin to vendor-patched versions that resolve this vulnerability.

Fix this in Irfanview Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-15248 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-15248 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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