You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

18 lines
1.1 KiB

4 years ago
# i am writing this atm so come back later
4 years ago
# badeye
4 years ago
Its well known that battleye proxies calls to `NtReadVirtualMemory/NtWriteVirtualMemory` to their driver via DeviceIoControl in both `lsass.exe` and `csrss.exe`. Although csrss.exe
is not something you can inject from usermode, lsass.exe is (although it can be protected, depends on your system/hvci).
4 years ago
4 years ago
The reason this proxy of a syscall is a vulnerability is simply because their is no validation of R/W access on the specified handle passed to `BEDaisy`. In other words: you can
open a handle with `PROCESS_QUERY_LIMITED_INFORMATION` and use that handle to read/write any usermode memory that is also read/writeable. The handle access is not important to bedaisy
4 years ago
rather they use the handle to get the EPROCESS of the process that the handle is opened on.
4 years ago
<img src="https://imgur.com/5MjFoHg.png"/>
4 years ago
4 years ago
As you can see you can open any handle with any access and then pass it along to bedaisy and it will read/write for you...
# lsass.exe/csrss.exe
This section will go into detail about what exactly is going on here. csrss.exe/lsass.exe have handles to all processes