The problem is, how do we know which memory to overwrite? Do we have access to that program's memory, especially the parts containing the instructions we want to change? You can write to another process' memory but it's more complicated.
#Cp wpe pro download code
(This principal is also the reason you have to be careful writing programs in low-level languages like C since if you put bad stuff in bad parts of RAM, it can crash the program or open you up to shell code exploits). The answer is yes and will provide us the means of messing with another application - in this case, telling it to send some data over its open socket. What does this imply? Well, if the application's code is all in RAM, can we change the application's code while it's running by just changing some of its memory? After all, it's just a bunch of instructions. The compiled code is all being put into RAM. When you double-click an executable, Windows parses it and loads its code, etc. The whole entire process of what I'm about to explain to you boils down to this very principal. The very basics of how EXEs are executed:
#Cp wpe pro download how to
Are you asking how to make someone else's program send data over its existing Winsock connection?
0 kommentar(er)
