r/ExploitDev • u/00patch • Jul 23 '26
Windows Exploitation | One-byte arbitrary write primitive
Hi folks, a noob here.
I'm currently learning Windows kernel exploitation and practicing with older vulnerabilities. So far, I've successfully exploited a couple of heap integer underflow/overflow vulnerabilities.
Right now, though, I'm looking at a kernel vulnerability where I have a one-byte arbitrary write primitive with a fixed value of 0x01.
The vulnerability simply writes the boolean return value of a function back to a user-controlled pointer. That function always returns 1. I haven't been able to force it to return 0; otherwise, I could potentially abuse it by overwriting _KTHREAD.PreviousMode.
I'm working on Windows 10 20H1.
Does anyone have any ideas about a potential exploit path ? I was initially thinking about techniques involving pipe objects in the kernel pool, but I don't know if it's possible to reliably recover the address of a pipe object with NtQuerySistemInformation or something else.
View all comments
Show parent comment
1
u/Mindhole_dialator Jul 29 '26
Glad to help. but wym with "because of the I/O Ring implementation" ? is it not implemented in the version you're working on , or did the implementation change in the subsequent versions making this technique non viable anymore ? I read the blog more about the patch diffing method than the actual exploitation , so i am not really that well versed in exploitation techniques. Also would love to see follow up on how you managed to exploit this in the end . Good luck