https://github.com/uefi-code/windowsdanger
A REALLY Danger Windows Driver, Turn Any threads Ring0!
https://github.com/uefi-code/windowsdanger
kernel-hacking ring0 rootkit toy-computer windows-driver windows-kernel-development x86-64
Last synced: 1 day ago
JSON representation
A REALLY Danger Windows Driver, Turn Any threads Ring0!
- Host: GitHub
- URL: https://github.com/uefi-code/windowsdanger
- Owner: UEFI-code
- Created: 2023-06-13T03:35:00.000Z (about 2 years ago)
- Default Branch: main
- Last Pushed: 2025-03-18T09:58:12.000Z (4 months ago)
- Last Synced: 2025-05-17T03:33:16.471Z (about 2 months ago)
- Topics: kernel-hacking, ring0, rootkit, toy-computer, windows-driver, windows-kernel-development, x86-64
- Language: C
- Homepage:
- Size: 98.6 MB
- Stars: 8
- Watchers: 2
- Forks: 3
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Citation: CITATION.cff
Awesome Lists containing this project
README
# WindowsDanger
WindowsDanger is an open-source project that help developers to Learn Windows Kernel and other x86 Features.
**But, We are NOT modify/patch Windows Code**
**We Directly Modify x86 Context Instead**
**So, We will not bypass PatchGuard, Using Official Test-Mode Instead**
This driver **Dreamed** to assist developers accessing and manipulating system resources more conveniently. By installing and launching this driver, you can elevate all threads to Ring0, allowing for full control over low-level hardware and system resources.
⚠️ **Warning**: Please be aware that using WindowsDanger may result in system instability, data loss, or other unintended consequences. Use with caution and perform testing in a safe environment.
This project is still under development. For more quick access, please use the [QEMU_Danger_x86](https://github.com/UEFI-code/QEMU_Danger_x86) project.
```Ke386SetIoAccessMap``` and ```Ke386IoSetAccessProcess``` is NOT available in Win10/Server 2019 and above. It's better to learn how the x86 CPU work within TSS and IOPM.
Currently achieved:
- Disable Write-Protection by modifiy CR0
- Hack Ring3 Segment in GDT to Ring0
- Insert new user-callable IDT entries 78H and 79H, 78H will return back normally, while 79H will hack user thread's CS & SS to Ring0
- Disable SMAP/SMEP by modify CR4
- Adapt Multi-Processor System
Known Issues:
- After EXE entered Ring0, the kernel-thread-switch may not working properly, and will result in BSOD. To avoid this, we need back to Ring3 quickly after we played !! See [InterruptTester](UserMode_InterruptTester) for more details.
Ideas:
- Use soft ```int``` instruct from Ring3, and hack stack for return CS RPL -> 0, then ```iretq```.
## Features
- Elevate any threads to Ring0 for full control over low-level system resources by simply `int 079h`
- Facilitate hardware debugging and reverse engineering tasks
- Tested on Windows Server 2022 x64, on Hyper-V
## Installation
**MUST Attach Kernel Debugger to prevent BSOD**, because ```int 3``` will trigger BSOD without Kernel Debugger.
1. Download the latest version of the WindowsDanger driver.
2. Copy the driver file to an appropriate directory (e.g., `C:\Windows\System32\drivers`).
3. Run the following command with administrator privileges to install the driver:
```C
sc create WindowsDanger type= kernel binPath= C:\Windows\System32\drivers\WindowsDanger.sys
```
4. Start the driver:
```C
sc start WindowsDanger
```
## Play
- [IoCTL_Caller](UserMode_Caller): Send Requests to our Kernel Driver. Supported Commands:
- 0 : Disable Write-Protection by modifiy CR0
- 1 : Hack Ring3 Segment in GDT to Ring0
- 2 : Mapping CR3 to a Virtual Address
- 3 : Insert new user-callable IDT entries 78H and 79H
- 4 : Disable SMAP/SMEP by modify CR4
- [InterruptTester](UserMode_InterruptTester): Test our new IDT entries 78H and 79H
- 78H : Return back normally
- 79H : Hack current thread's CS & SS to Ring0 !!
**Please note, before you use `int 079h`, you must Hack the GDT, Disable SMAP/SMEP, and Insert new IDT entries by (1, 4, 3).**
## Uninstallation
1. Stop the driver:
```C
sc stop WindowsDanger
```
2. Remove the driver:
```C
sc delete WindowsDanger
```
3. Delete the driver file.
## Learning Resources
0. [Lab Experiment HandBooks](LabHandBooks): Contains Microsoft Learn Student Ambassador Workshop
1. Download the WinDbg Preview tool from the Microsoft Store or [Non Store](DownloadWinDbgPreviewNonStore)
2. Install [WDK](https://learn.microsoft.com/zh-cn/windows-hardware/drivers/download-the-wdk?wt.mc_id=studentamb_188195)
3. Read [Kernel Debugging Document](https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/setting-up-a-network-debugging-connection?wt.mc_id=studentamb_188195) on the Microsoft Learn
4. Read [My Experiment log](Experiment_Record_GPT4.md) for more details
5. Cource: [Arch2001_x86-64_OS_Internals](https://apps.p.ost2.fyi/learning/course/course-v1:OpenSecurityTraining2+Arch2001_x86-64_OS_Internals+2021_v1/home)
## License
WindowsDanger is licensed under the [MIT License](LICENSE). Please refer to the [LICENSE](LICENSE) file for more information.
## Contributing
We welcome your contributions to the WindowsDanger project! Please see [CONTRIBUTING.md](CONTRIBUTING.md) for how to get started.
## Support and Feedback
If you encounter any issues while using WindowsDanger, or have any suggestions and feedback, please submit your concerns on the [Issues](https://github.com/UEFI-code/WindowsDanger/issues) page.
## Disclaimer
WindowsDanger is intended for learning and research purposes only. The use of this driver may result in system instability, data loss, or other unintended consequences. The project authors and contributors are not responsible for any damages or losses resulting from the use of this driver. By using WindowsDanger, you agree to assume all risks.