Microsoft Windows up to Server 2019 Win32k privileges management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in Microsoft Windows. It has been classified as critical. The affected element is an unknown function of the component Win32k. The manipulation leads to Local Privilege Escalation. This vulnerability is uniquely identified as CVE-2020-17057. Local access is required to approach this attack. No exploit exists. It is recommended to apply a patch to fix this issue.
Details
A vulnerability was found in Microsoft Windows (Operating System) and classified as critical. This issue affects an unknown code block of the component Win32k. The manipulation with an unknown input leads to a local privilege escalation vulnerability. Using CWE to declare the problem leads to CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. Impacted is confidentiality, integrity, and availability.
The weakness was disclosed 11/10/2020 as confirmed security guidance (Website). It is possible to read the advisory at portal.msrc.microsoft.com. The identification of this vulnerability is CVE-2020-17057. The exploitation is known to be difficult. Attacking locally is a requirement. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 12/05/2020). The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
Version
- 10 20H2
- 10 1607
- 10 1803
- 10 1809
- 10 1903
- 10 1909
- 10 2004
- Server 20H2
- Server 1903
- Server 1909
- Server 2004
- Server 2012 R2
- Server 2016
- Server 2019
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: 7.3VulDB Meta Temp Score: 6.7
VulDB Base Score: 7.0
VulDB Temp Score: 6.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 7.0
Vendor Vector (Microsoft): 🔍
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: Privileges managementCWE: CWE-269 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Unproven
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: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
08/04/2020 🔍11/10/2020 🔍
11/10/2020 🔍
11/11/2020 🔍
12/05/2020 🔍
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: portal.msrc.microsoft.com
Status: Confirmed
CVE: CVE-2020-17057 (🔍)
GCVE (CVE): GCVE-0-2020-17057
GCVE (VulDB): GCVE-100-164687
scip Labs: https://www.scip.ch/en/?labs.20161215
Entry
Created: 11/11/2020 10:27Updated: 12/05/2020 10:56
Changes: 11/11/2020 10:27 (25), 11/11/2020 10:28 (8), 11/11/2020 10:31 (19), 12/05/2020 10:50 (3), 12/05/2020 10:56 (20)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.