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 3e71169f8f
commit 8914c33963
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File

2
README.md
Unescape View File

@ -13,7 +13,7 @@ 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 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
(like MSI Afterburner), or general windows system utilities that expose physical read/write. (like MSI Afterburner), or general windows system utilities that expose physical read/write.

Write Preview
Loading…
Cancel
Save