
Tavis Ormandy
@taviso
Vulnerability researcher at Google. This is a personal stream, opinions expressed are mine. I'm also @[email protected]
ID: 14453232
https://lock.cmpxchg8b.com/ 20-04-2008 17:19:37
9,9K Tweet
130,130K Followers
627 Following

No surprises here, but CrowdStrike confirms Tavis Ormandy's analysis, that the bug was indeed not due to a NULL-pointer deference 🧠 ...but rather "an out-of-bounds memory read"




CrowdStrike This 100% matches our/Tavis Ormandy's conclusions derived from analyzing the crash report/disasm 🧠 RAX: input pointer array R11: index (0x14/20d) Accessing Array[20] retrieved the 21st item (as arrays are 0-based). This returned an invalid memory address that 💥'd when deref'd!
![Patrick Wardle (@patrickwardle) on Twitter photo <a href="/CrowdStrike/">CrowdStrike</a> This 100% matches our/<a href="/taviso/">Tavis Ormandy</a>'s conclusions derived from analyzing the crash report/disasm 🧠
RAX: input pointer array
R11: index (0x14/20d)
Accessing Array[20] retrieved the 21st item (as arrays are 0-based). This returned an invalid memory address that 💥'd when deref'd! <a href="/CrowdStrike/">CrowdStrike</a> This 100% matches our/<a href="/taviso/">Tavis Ormandy</a>'s conclusions derived from analyzing the crash report/disasm 🧠
RAX: input pointer array
R11: index (0x14/20d)
Accessing Array[20] retrieved the 21st item (as arrays are 0-based). This returned an invalid memory address that 💥'd when deref'd!](https://pbs.twimg.com/media/GUY3Zoea8AMSaBS.jpg)




Fuzzing Windows Defender in the Honggfuzz+IntelPT (hardware) mode scrapco.de/blog/fuzzing-w… by @[email protected]

