AppCheck/AppCheck Pro up to 2.0.1.14 Executable Loader 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 AppCheck and AppCheck Pro up to 2.0.1.14. It has been rated as problematic. This impacts an unknown function of the component Executable Loader. The manipulation leads to untrusted search path. This vulnerability is documented as CVE-2017-2214. The attack needs to be performed locally. There is not any exploit available. Upgrading the affected component is advised.
Details
A vulnerability was found in AppCheck and AppCheck Pro up to 2.0.1.14. It has been rated as problematic. This issue affects an unknown function of the component Executable 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. The summary by CVE is:
Untrusted search path vulnerability in AppCheck and AppCheck Pro prior to version 2.0.1.15 allows an attacker to execute arbitrary code via a specially crafted executable file in an unspecified directory.
The bug was discovered 06/07/2017. The weakness was released 06/09/2017 (Website). The advisory is shared at jvn.jp. The identification of this vulnerability is CVE-2017-2214 since 12/01/2016. An attack has to be approached locally. The successful exploitation requires a simple authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1574 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 2.0.1.15 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
- 2.0.1.0
- 2.0.1.1
- 2.0.1.2
- 2.0.1.3
- 2.0.1.4
- 2.0.1.5
- 2.0.1.6
- 2.0.1.7
- 2.0.1.8
- 2.0.1.9
- 2.0.1.10
- 2.0.1.11
- 2.0.1.12
- 2.0.1.13
- 2.0.1.14
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.7
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.4
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: AppCheck/AppCheck Pro 2.0.1.15
Timeline
12/01/2016 🔍06/07/2017 🔍
06/09/2017 🔍
06/09/2017 🔍
06/10/2017 🔍
10/16/2019 🔍
Sources
Advisory: jvn.jpStatus: Not defined
CVE: CVE-2017-2214 (🔍)
GCVE (CVE): GCVE-0-2017-2214
GCVE (VulDB): GCVE-100-102221
Entry
Created: 06/10/2017 09:03Updated: 10/16/2019 09:25
Changes: 06/10/2017 09:03 (58), 10/16/2019 09:25 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.