Intel Extreme Tuning Utility up to 6.4.1.20 memory corruption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Intel Extreme Tuning Utility up to 6.4.1.20. It has been classified as problematic. The impacted element is an unknown function. Performing a manipulation results in memory corruption. This vulnerability was named CVE-2018-12149. The attack needs to be approached locally. There is no available exploit. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as problematic, was found in Intel Extreme Tuning Utility up to 6.4.1.20. This affects an unknown code block. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Buffer overflow in input handling in Intel Extreme Tuning Utility before 6.4.1.21 may allow an authenticated user to potentially deny service to the application via local access.
The bug was discovered 09/11/2018. The weakness was presented 09/12/2018 (Website). The advisory is shared at intel.com. This vulnerability is uniquely identified as CVE-2018-12149 since 06/11/2018. An attack has to be approached locally. The requirement for exploitation is a authentication. Neither technical details nor an exploit are publicly available.
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 $5k-$25k.
Upgrading to version 6.4.1.21 eliminates this vulnerability.
See VDB-123934 and VDB-123935 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
- 6.4.1.0
- 6.4.1.1
- 6.4.1.2
- 6.4.1.3
- 6.4.1.4
- 6.4.1.5
- 6.4.1.6
- 6.4.1.7
- 6.4.1.8
- 6.4.1.9
- 6.4.1.10
- 6.4.1.11
- 6.4.1.12
- 6.4.1.13
- 6.4.1.14
- 6.4.1.15
- 6.4.1.16
- 6.4.1.17
- 6.4.1.18
- 6.4.1.19
- 6.4.1.20
License
Website
- Vendor: https://www.intel.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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: Extreme Tuning Utility 6.4.1.21
Timeline
06/11/2018 🔍09/11/2018 🔍
09/12/2018 🔍
09/12/2018 🔍
09/13/2018 🔍
03/23/2020 🔍
Sources
Vendor: intel.comAdvisory: intel.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-12149 (🔍)
GCVE (CVE): GCVE-0-2018-12149
GCVE (VulDB): GCVE-100-123933
See also: 🔍
Entry
Created: 09/13/2018 06:58Updated: 03/23/2020 08:13
Changes: 09/13/2018 06:58 (58), 03/23/2020 08:13 (2)
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.