|
Attack Vector Test Platform
|
|
Hits: 46 |
|
Date added: 06/13/2006 |
|
The Attack Vector Test Platform was written over the course of research for the paper and presentation titled A Comparison Buffer Overflow Prevention Implementations Weaknesses which was presented at the 2004 Black Hat and Defcon computer security conferences. The test platform allows for assessing the effectiveness of combinations of attack buffer placement and execution control vectors against various buffer overflow prevention software technologies. |
|
|
|
|
|
notSPIKEfile
|
|
Hits: 26 |
|
Date added: 07/08/2006 |
|
notSPIKEfile is a linux based file format fuzzing tool. It was designed to automate the executing the launching of applications and detection of exceptions caused by fuzzed file formats. |
|
|
|
|
|
FileFuzz
hot!
|
|
Hits: 79 |
|
Date added: 07/23/2006 |
|
FileFuzz is a graphical Windows based file format fuzzing tool. FileFuzz was designed to automate the executing the launching of applications and detection of exceptions caused by fuzzed file formats. |
|
|
|
|
|
|
Buffer Example
|
|
Hits: 46 |
|
Date added: 11/14/2006 |
|
Example code for any one wanting to see real example.
Source code included. |
|
|
|
|
|
|
uhooker v1.2
hot!
|
|
Hits: 63 |
|
Date added: 09/10/2007 |
|
The Universal Hooker is a tool to intercept execution of programs. It enables the user to intercept calls to API calls inside DLLs, and also arbitrary addresses within the executable file in memory.
Why is it 'Universal'? There are different ways of hooking functions in a program, for example, it can be done by setting software breakpoints (int 3h), hardware breakpoints (cpu regs), or overwriting the prologue of a function to jump to a 'stub', etc. All the methods mentioned required above, specially the latter, require the programmer of the code creating the hook to have certain knowledge of the function it is intercepting. If the code is written in a programming language like C/C++, the code will normally need to be recompiled for every function one wants to intercept, etc.
The Universal Hooker tries to create very simple abstractions that allow a user of the tool to write hooks for different API and non-API functions using an interpreted language (python), without the need to compile anything, and with the possibility of changing the code that gets executed whent the hooked function is called in run-time.
The Universal Hooker builds on the idea that the function handling the hook is the one with the knowledge about the parameters type of the function it is handling. The Universal Hooker only knows the number of parameters of the function, and obtains them from the stack (all DWORDS). The hook handler is the one that will interpret those DWORDS as the types received by the function.
The hook handlers are written in python, what eliminates the need for recompiling the handlers when a modification is required. And also, the hook handlers (executed by the server) are reloaded from disk every time a hook handler is called, this means that one can change the behavior of the hook handler without the need to recompile the code, or having to restart the application being analyzed. |
|
|
|
