Protecting software integrity is a key to successfully maintain its own credibility and reduce the financial and technical risks caused from a lack of integrity. Although researchers have been putting effort on improving software development techniques and preventing human errors during the software development process, it is still a daunting task to make non-vulnerable software in practice. For example, the national vulnerability database shows that a set of new software vulnerabilities are discovered every day.(1) --4169-- Checking memory write to AFEFE8B8 of size 4 (1) --4169-- $ebp setting for RespondeHTTPPendiente - ebp: ... Therefore, it is non-trivial to locate the corrupting instruction using gdb, if not entirely impossible. ... debugging mode from the last asafe pointa (0x8050136), detected the (illegal) memory write into the return address in the stack frame of the main function, and raised a flag accordingly.
|Title||:||Mechanisms for Protecting Software Integrity in Networked Systems|
|Publisher||:||ProQuest - 2008|