|
Same way you found the first pointer, Why not just click "what access/write" this address on the pointer you added after you know its correct, but I don't think I've had any addresses that were pointers pointing to another pointer, Lol. Most that I've had were either static or base+offset, The opcode around the original pointer should give some clues, or you can check what value the pointer of that address is most likely holding via more info after opening assembly scan with write/access.
I don't think its too much more complicated to find a 2nd pointer if that even exists, I mean its possible to make a invalid pointer but have it still come out pointing to the correct address for that launch but its probably unlikely. Can't really test it because the addresses your talking about aren't commonly scanned for example dung entry hack.
Don't really have any characters to throw away using dung dc scans for those addresses.
|