# CVE-2024-37726 MSI Center Local Privilege Escalation - Arbitrary File Overwrite Vulnerability
# Vulnerability Summary
A local privilege escalation vulnerability on Windows OS has been identified in MSI Center versions <= 2.0.36.0, which allows a low-privileged user to arbitrarily overwrite or delete high-privileged and critical files on a system. This vulnerability is caused by the MSI Center application running with NT AUTHORITY\SYSTEM privileges and writing the file to a low privilege user controlled directory, which allows a low-privileged user to manipulate the file system with symlink and trick the application into writing or overwriting files in arbitrary locations.
# **Vulnerability Details**
The vulnerability is triggered when a low-privileged user creates a directory and sets an OpLock on a file within that directory. The user can then utilize the "Export System Info" function in MSI Center to trigger a file write operation on the OpLocked file. While the OpLock is in place, the user can move the original file and create a junction to a target file, allowing the MSI Center application to overwrite or delete the target file with SYSTEM privileges.
# **Steps to Reproduce**
1. Create a directory with a single file (e.g., C:\Users\Public\eop\12345.txt).
2. Set an OpLock on the file 12345.txt.
3. Choose the "Export System Info" function in MSI Center and select the OpLocked file to trigger a file write operation.
4. The MSI Center.exe and MSI.CentralServer.exe processes will be paused due to the OpLock.
5. Move the 12345.txt to empty the directory.
6. Create a junction from the original directory to a target location (e.g., GLOBAL\GLOBALROOT\RPC Control\12345.txt).
7. Create a symbolic link from the target location to the target file (e.g., C:\Windows\lsasetup.log).
8. Release the OpLock.
9. Delete the symbolic link.
10. The target file (e.g., C:\Windows\lsasetup.log) will be deleted and overwritten.
# Privilege Escalation
We could create and install the program without admin right, install it on anyway that low privilege user have write access. As the output contain the name of the installed program, we can abuse the program name, write the result to C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\backdoor.bat. Whenever an administrator login, they will execute our payload and cause privilege escalation.
Be sure to user MsiInfo.exe to remove the admin requirement of installation.
```powershell
C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x86\MsiInfo.exe "D:\tools\MSI Center EOP\t& calc.exe &\Release\t& calc.exe &.msi" -w 10
```
# **Steps of Privilege Escalation**
1) With Low privilege user, create and install the program with payload as program name.
2) Re-run the poc but point the link to C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\calc.bat
3) Observed that our payload has included in the output.
4) By abusing the autorun features, when an administrator login, we could trick them to run arbitrary code.
# **Impact**
A successful exploitation of this vulnerability allows a low-privileged user to arbitrarily overwrite or delete critical system files, leading to a potential escalation of privileges. This could result in a complete compromise of the system.
# Remark
A new version (2.0.38.0) has been released on 3/7/2024 and fixed the vulnerability.
[4.0K] /data/pocs/a8ab1d461d570c4e2064cf54ce95485f38ab02b6
├── [4.0K] CVE-2024-37726 MSI Center Local Privilege Escalati 0fff3750575149f29933d4a87bbd3164
│ ├── [ 19K] Untitled 1.png
│ ├── [ 56K] Untitled 2.png
│ ├── [ 57K] Untitled 3.png
│ ├── [ 42K] Untitled 4.png
│ ├── [732K] Untitled 5.png
│ └── [117K] Untitled.png
├── [4.0K] MSI Center EOP
│ ├── [2.3K] def.h
│ ├── [4.1K] FileOplock.cpp
│ ├── [ 946] FileOpLock.h
│ ├── [1.4K] PoC.sln
│ ├── [6.7K] PoC.vcxproj
│ ├── [1.4K] PoC.vcxproj.filters
│ ├── [ 165] PoC.vcxproj.user
│ ├── [1.2M] resource.aps
│ ├── [ 435] resource.h
│ ├── [1.4K] resource.rc
│ └── [8.8K] Source.cpp
└── [4.0K] README.md
2 directories, 18 files