SYSTEM code execution via temporary-directory DLL preloading
Published Apr 12, 2022 · Updated Oct 1, 2024
DLL hijacking in Git for Windows bundled with affected Microsoft Visual Studio releases allows local users to execute code as SYSTEM. The uninstaller copies a component into the SYSTEM account's C:\Windows\Temp directory and loads DLLs from that world-writable location without constraining the search path. An authenticated local user must plant a malicious DLL there and wait for the uninstaller to run as SYSTEM; successful exploitation executes the DLL with SYSTEM privileges.
Summary
What happened
DLL hijacking in Git for Windows bundled with affected Microsoft Visual Studio releases allows local users to execute code as SYSTEM. The uninstaller copies a component into the SYSTEM account's C:\Windows\Temp directory and loads DLLs from that world-writable location without constraining the search path. An authenticated local user must plant a malicious DLL there and wait for the uninstaller to run as SYSTEM; successful exploitation executes the DLL with SYSTEM privileges.
The record
- CVE
- CVE-2022-24767
- Published
- Apr 12, 2022
- Updated
- Oct 1, 2024
- Vendor
- Microsoft
- Product
- Microsoft Visual Studio 2019
- Classifications
- CWE-427, CWE-378, T1574.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 12, 2022CVE publishedPublication date reported by the CVE source.
- Oct 1, 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