From 323255948ceecace02c3f95693b184d63abb0303 Mon Sep 17 00:00:00 2001 From: xerox Date: Sun, 19 Apr 2020 09:38:50 +0000 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 2950c2e..c36f7dd 100644 --- a/README.md +++ b/README.md @@ -21,7 +21,7 @@ Any driver exposing MmMapIoSpace/MmUnmapIoSpace or ZwMapViewOfSection/ZwUnmapVie Ff you are in any sort of doubt about the abundance of these drivers simply go to this page and ctrl-f "MmMapIoSpace". -## How does it work? +### How does this exploit work? First lets start with a given, controlled writes can be leveraged to gain execution. I think people call this "write what where", but nevertheless if you know where you are writing you can leverage it to gain execution in places that might not have been accessable proir. Now that we have that agreed upon, lets get into the details of how this works.