IDontCode
/
physmeme
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update README.md

Browse Source
merge-requests/1/head
xerox 5 years ago
parent e50552686b
commit 10cec9cd2a
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File

6
README.md
Unescape View File

@ -12,6 +12,12 @@ Before I begin, those who helped me create this project shall be credited.
Given map/unmap (read/write) of physical memory, one can now systematically map unsigned code into ones kernel. Given map/unmap (read/write) of physical memory, one can now systematically map unsigned code into ones kernel.
Many drivers expose this primitive and now can all be exploited by simply coding a few functions. Many drivers expose this primitive and now can all be exploited by simply coding a few functions.
### What versions of windows does this mapper support?
This mapper should work without any issues for pretty much all versions of relevant windows. Tested on windows 10 (1803-1909), but should support all the way back to vista.
<img src="https://cdn.discordapp.com/attachments/693313068247285821/701219951733768232/unknown.png"/>
### What drivers support physical read/write? ### What drivers support physical read/write?
Any driver exposing MmMapIoSpace/MmUnmapIoSpace or ZwMapViewOfSection/ZwUnmapViewOfSection can be exploited. This means bios flashing utils, fan speed utils Any driver exposing MmMapIoSpace/MmUnmapIoSpace or ZwMapViewOfSection/ZwUnmapViewOfSection can be exploited. This means bios flashing utils, fan speed utils

Write Preview
Loading…
Cancel
Save