![]() |
|
#1
|
|||
|
|||
|
Creating a buffer overflow ?
As I understand it most buffer overflow exploits must be found by the cracker, and it must be able to influence the target variable once the overflow has occured.
Instead of just finding these overflow exploits, wouldn't it be possible to in fact force the buffer to overflow? i.e, If you somehow were able to manipulate the values of the bounds? i.e Quote:
What I'm saying is that when you disassemble the program you should search for where that [10] is assigned in asm, and then change it to a [0]. That way the overflow would always occur. Of course you probably wouldn't change the asm code, but you could do a live memory hack, like a simple game trainer does to change the [10] to a [0]. Last edited by Rhodium; 08-17-2003 at 15:33. |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| OllyDBG v1.10 and ImpREC v1.7f export name buffer overflow vulnerability | bukkake | General Discussion | 0 | 07-28-2008 03:40 |
| Buffer Overflow in SentinelLM Service | prt | General Discussion | 0 | 03-19-2005 05:20 |
| DataRescue Interactive Disassembler Pro Buffer Overflow Vulnerability | bukkake | General Discussion | 0 | 01-25-2005 11:23 |