Microsoft Windows up to Server 2019 CSC Service privileges management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Microsoft Windows. Affected by this vulnerability is an unknown functionality of the component CSC Service. Performing a manipulation results in an unknown weakness. This vulnerability was named CVE-2021-1652. The attack needs to be approached locally. There is no available exploit. It is suggested to install a patch to address this issue.
Details
A vulnerability, which was classified as critical, was found in Microsoft Windows (Operating System). This affects some unknown functionality of the component CSC Service. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was presented 01/12/2021 as confirmed security guidance (Website). The advisory is shared at portal.msrc.microsoft.com. This vulnerability is uniquely identified as CVE-2021-1652. 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 10/09/2024). MITRE ATT&CK project uses the attack technique T1068 for this issue.
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 7 SP1
- 8.1
- 10
- 10 20H2
- 10 1607
- 10 1803
- 10 1809
- 10 1909
- 10 2004
- RT 8.1
- Server 20H2
- Server 1909
- Server 2004
- Server 2008 R2 SP1
- Server 2008 SP2
- Server 2012
- 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.8VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.8
VulDB Temp Score: 6.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 7.8
Vendor Vector (Microsoft): 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CNA Base Score: 7.8
CNA 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
12/02/2020 🔍01/12/2021 🔍
01/12/2021 🔍
01/13/2021 🔍
10/09/2024 🔍
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: portal.msrc.microsoft.com
Status: Confirmed
CVE: CVE-2021-1652 (🔍)
GCVE (CVE): GCVE-0-2021-1652
GCVE (VulDB): GCVE-100-167673
scip Labs: https://www.scip.ch/en/?labs.20161215
Entry
Created: 01/13/2021 10:08Updated: 10/09/2024 01:09
Changes: 01/13/2021 10:08 (9), 01/13/2021 10:09 (25), 01/13/2021 10:13 (19), 02/12/2021 06:55 (2), 02/12/2021 07:00 (18), 10/09/2024 01:09 (25)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.