![]() |
|
#2
|
||||
|
||||
|
What would be the point of this? Considering the fact that most buffer exploits are doing over the intenet, where you don't have access to the machine to change any of the assembler - you only have the interface of the program that is running.
Secondly, once the program has compiled, trying to change a static buffer size to less than it was orignally set to would be very difficult, as if it was a global variable, it would most likely be a space in the exe, and local variables would simply be space on the stack. |
|
|
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 |