Microsoft Windows IExpress Archive File untrusted search path
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in Microsoft Windows. It has been classified as problematic. Affected by this issue is some unknown functionality of the component IExpress. Performing a manipulation as part of Archive File results in untrusted search path. This vulnerability is identified as CVE-2018-0598. The attack is only possible with local access. There is not any exploit available.
Details
A vulnerability, which was classified as problematic, was found in Microsoft Windows (Operating System) (unknown version). This affects an unknown code block of the component IExpress. The manipulation as part of a Archive File leads to a untrusted search path vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Untrusted search path vulnerability in Self-extracting archive files created by IExpress bundled with Microsoft Windows allows an attacker to gain privileges via a Trojan horse DLL in an unspecified directory.
The bug was discovered 05/17/2018. The weakness was released 06/26/2018 (Website). The advisory is shared at jvn.jp. This vulnerability is uniquely identified as CVE-2018-0598 since 11/27/2017. An attack has to be approached locally. The requirement for exploitation is a authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 02/22/2020). 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 40 days. During that time the estimated underground price was around $25k-$100k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.microsoft.com/
- Product: https://www.microsoft.com/en-us/windows
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
11/27/2017 🔍05/17/2018 🔍
06/26/2018 🔍
06/26/2018 🔍
06/26/2018 🔍
02/22/2020 🔍
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: jvn.jp
Status: Not defined
CVE: CVE-2018-0598 (🔍)
GCVE (CVE): GCVE-0-2018-0598
GCVE (VulDB): GCVE-100-119901
Entry
Created: 06/27/2018 00:29Updated: 02/22/2020 08:18
Changes: 06/27/2018 00:29 (63), 02/22/2020 08:18 (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.