PatchJGD DLL Loader PatchJGDh101.EXE untrusted search path
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in PatchJGD and classified as problematic. The affected element is an unknown function of the file PatchJGDh101.EXE of the component DLL Loader. Such manipulation leads to untrusted search path. This vulnerability is listed as CVE-2017-2211. The attack must be carried out locally. There is no available exploit.
Details
A vulnerability was found in PatchJGD (the affected version is unknown) and classified as problematic. Affected by this issue is an unknown code of the file PatchJGDh101.EXE of the component DLL Loader. The manipulation with an unknown input leads to a untrusted search path vulnerability. Using CWE to declare the problem leads to CWE-426. The product searches for critical resources using an externally-supplied search path that can point to resources that are not under the product's direct control. Impacted is confidentiality, integrity, and availability. CVE summarizes:
Untrusted search path vulnerability in PatchJGD (Hyoko) (PatchJGDh101.EXE) ver. 1.0.1 allows an attacker to gain privileges via a Trojan horse DLL in an unspecified directory.
The bug was discovered 06/08/2017. The weakness was presented 06/09/2017 (Website). The advisory is available at jvn.jp. This vulnerability is handled as CVE-2017-2211 since 12/01/2016. Local access is required to approach this attack. A simple authentication is needed for exploitation. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1574 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-102217, VDB-102219 and VDB-102220 for similar entries. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Untrusted search pathCWE: CWE-426
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/01/2016 🔍06/08/2017 🔍
06/09/2017 🔍
06/09/2017 🔍
06/10/2017 🔍
10/16/2019 🔍
Sources
Advisory: jvn.jpStatus: Not defined
Confirmation: 🔍
CVE: CVE-2017-2211 (🔍)
GCVE (CVE): GCVE-0-2017-2211
GCVE (VulDB): GCVE-100-102218
See also: 🔍
Entry
Created: 06/10/2017 09:03Updated: 10/16/2019 09:13
Changes: 06/10/2017 09:03 (58), 10/16/2019 09:13 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.