Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2017-2210: Untrusted search path vulnerability in PatchJGD (PatchJGD101.EXE) ver

42
This month
HIGH 7.8DOWNGRADE

CVE-2017-2210 is a high-severity flaw (CVSS 7.8) affecting patchjgd. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Untrusted search path vulnerability in PatchJGD (PatchJGD101.EXE) ver. 1.0.1 allows an attacker to gain privileges via a Trojan horse DLL in an unspecified directory.

Why this priority

  • High severity

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score7.8 (High)
Attack vectorLocal
Attack complexityLow
Privileges neededNone
User interactionRequired
EPSS exploit chance0.9% (top 41%)
CISA exploited listNo
WeaknessCWE-427
Published2017-06-09
Last modified2026-06-17
Publisher (CNA): JPCERT/CC · Vendor: gsi

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

gsi patchjgd DOWNGRADE
Affected: 1.0.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.0.1
1. Check installed version
apt-cache policy patchjgd || rpm -q patchjgd || patchjgd --version
2. No fixed release: DOWNGRADE to a release before 1.0.1 (Debian / Ubuntu)
apt-cache madison patchjgd sudo apt install patchjgd=<VERSION_BEFORE_1.0.1> sudo apt-mark hold patchjgd
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list patchjgd sudo dnf downgrade patchjgd-<VERSION_BEFORE_1.0.1> sudo dnf versionlock add patchjgd
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-2210?

patchjgd: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-2210 being exploited?

CVE-2017-2210 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-2210 affect?

CVE-2017-2210 affects patchjgd. Severity is high (CVSS 7.8). Untrusted search path vulnerability in PatchJGD (PatchJGD101.EXE) ver. 1.0.1 allows an attacker to gain privileges via a Trojan horse DLL in an unspecified directory.

How urgent is CVE-2017-2210?

Priority 42/100. High severity

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.