Microsoft Windows up to Server 2019 State Repository Service privileges management

Summaryinfo

A vulnerability labeled as critical has been found in Microsoft Windows. Impacted is an unknown function of the component State Repository Service. The manipulation results in privileges management. This vulnerability was named CVE-2020-1305. The attack may be performed from remote. There is no available exploit. It is advisable to implement a patch to correct this issue.

Detailsinfo

A vulnerability classified as critical has been found in Microsoft Windows (Operating System). Affected is an unknown part of the component State Repository Service. The manipulation with an unknown input leads to a privileges management vulnerability. 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. CVE summarizes:

An elevation of privilege vulnerability exists when the Windows State Repository Service improperly handles objects in memory, aka 'Windows State Repository Service Elevation of Privilege Vulnerability'.

The weakness was presented 06/09/2020 as confirmed security update guide (Website). The advisory is shared for download at portal.msrc.microsoft.com. The public release was coordinated in cooperation with the vendor. This vulnerability is traded as CVE-2020-1305. It is possible to launch the attack remotely. A authentication is necessary for exploitation. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 06/10/2020). The MITRE ATT&CK project declares the attack technique as T1068. The advisory points out:

An elevation of privilege vulnerability exists when the Windows State Repository Service improperly handles objects in memory. An attacker who successfully exploited this vulnerability could run arbitrary code in an elevated context.

Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.

See VDB-156352, VDB-156351, VDB-156350 and VDB-156349 for similar entries. Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Operating System

Vendor

• Microsoft

Name

• Windows

Version

• 10
• 10 1607
• 10 1709
• 10 1803
• 10 1809
• 10 1903
• 10 1909
• 10 2004
• Server 1803
• Server 1903
• Server 1909
• Server 2004
• Server 2016
• Server 2019

License

• commercial

Website

• Vendor: https://www.microsoft.com/
• Product: https://www.microsoft.com/en-us/windows

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion