Local SYSTEM escalation via rollback directory replacement
Published Mar 12, 2020 · Updated Aug 4, 2024
Improper filesystem handling in Microsoft Windows Installer allows local users to gain SYSTEM privileges during installation rollback. Windows Installer fails to keep the C:\Config.Msi rollback directory protected, allowing a low-privileged user to move or replace it and plant a rollback script that the service executes as SYSTEM. Exploitation requires local unprivileged code execution and filesystem manipulation during an installer rollback, and successful exploitation grants full SYSTEM-level control.
Summary
What happened
Improper filesystem handling in Microsoft Windows Installer allows local users to gain SYSTEM privileges during installation rollback. Windows Installer fails to keep the C:\Config.Msi rollback directory protected, allowing a low-privileged user to move or replace it and plant a rollback script that the service executes as SYSTEM. Exploitation requires local unprivileged code execution and filesystem manipulation during an installer rollback, and successful exploitation grants full SYSTEM-level control.
The record
- CVE
- CVE-2020-0814
- Published
- Mar 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- Microsoft
- Product
- Windows 10 Version 1909
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 12, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo