You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I see a small bug inside the SpiderPIC shellcode permutation program.
Many shellcodes rely on a trick to get a pointer to a string by using a call instruction followed by the string.
For example a shellcode that spawns a calc.exe will contain sush instructions:
callrbpdb0x63db0x61db0x6cdb0x63db0x00
and injecting trash instructions between them, or trying to substitude them will completely break the shellcode.
The text was updated successfully, but these errors were encountered:
Hi, I see a small bug inside the SpiderPIC shellcode permutation program.
Many shellcodes rely on a trick to get a pointer to a string by using a call instruction followed by the string.
For example a shellcode that spawns a calc.exe will contain sush instructions:
and injecting trash instructions between them, or trying to substitude them will completely break the shellcode.
The text was updated successfully, but these errors were encountered: