CVE Tools

CVE-2020-17416

Exploitation likely. EPSS gives it a 12% chance of exploitation in the next 30 days. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

  • Foxit ReaderAffected: 10.0.0.35798Upgrade to: not statedStated by: CVE record
  • Foxitsoftware Foxit ReaderAffected: ≤ 10.0.1.35811Upgrade to: after 10.0.1.35811Stated by: NVD
  • Foxitsoftware PhantompdfAffected: ≤ 10.0.1.35811Upgrade to: after 10.0.1.35811Stated by: NVD

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check which version of Foxit Reader or Foxit PhantomPDF your staff use (Help > About).
  2. Avoid opening PDF or image files from unknown or unsolicited sources in the meantime.
  3. Visit Foxit's security bulletins page to confirm which version fixes this issue and download the update.
  4. Update all installations of Foxit Reader and Foxit PhantomPDF to the patched version vendor-wide.
  5. Repeat this check periodically since Foxit regularly issues security updates.

What it is

From the CVE record

This vulnerability allows remote attackers to execute arbitrary code on affected installations of Foxit Reader 10.0.0.35798. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of JPEG2000 images. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated structure. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-11497.

In plain language

Written by AI from the record

Opening a specially crafted PDF or image file in Foxit Reader could let an attacker take over your computer, but this requires tricking you into opening the bad file first, and there's no evidence attackers are actively using it yet.

Out-of-bounds write (CWE-787) in Foxit Reader/PhantomPDF's JPEG2000 image parser allows arbitrary code execution when a victim opens a malicious file, with no authentication needed but user interaction required.

If you're affected

  • Full computer takeover
  • Malware installation
  • Data theft from infected PC
  • Operational disruption

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS96th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

12% chance of exploitation activity in the next 30 days, which ranks it in the 96th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

7 events over 2180 days, from the signal feeds we watch.

  1. EPSS band change0 → moderateepss band change
  2. Patch availablerecord updated
  3. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Scored 7.8 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Reader, not every advisory.