While the TAP+CLAW implementation seems to work fine on an Azure Ubuntu machine (despite the microcode update), it is finding ROP gadgets which are located in pages which are only readable and not executable (or writable), causing crashes.
I might be missing something in either the paper itself or how I'm using the code, but is this something you tried to handle? Or is there an assumption that readable and non-writable code will be executable?
I've attached the output along with the proc maps to show the permissions.
app-out.txt
proc-map.txt
Update: The logs are from tests using the debug flag, under pre-release it's having trouble finding a stack frame. Will investigate and update accordingly.
While the TAP+CLAW implementation seems to work fine on an Azure Ubuntu machine (despite the microcode update), it is finding ROP gadgets which are located in pages which are only readable and not executable (or writable), causing crashes.
I might be missing something in either the paper itself or how I'm using the code, but is this something you tried to handle? Or is there an assumption that readable and non-writable code will be executable?
I've attached the output along with the proc maps to show the permissions.
app-out.txt
proc-map.txt
Update: The logs are from tests using the debug flag, under pre-release it's having trouble finding a stack frame. Will investigate and update accordingly.