![]() |
Created by Shahmeran Gilani
over 6 years ago
|
|
What is a Buffer Overrun?
Why are buffer overruns a problem?
What type of functions are most common areas of buffer overruns?
When a buffer declared on a stack is overwritten by copying data larger that the buffer capacity is considered what type of overrun?
Where are variables declared on the stack located by?
Unchecked user input is passed into what unchecked function to produce a stack overrun?
What is the result of sending a unchecked string input into strcpy?
What is one way of finding out that a buffer overrun exploit is achievable?
What are some of the uses of using perl?
What are other examples of overruns?
What is the easiest method to prevent a Buffer overrun?
What is Safe String Handling?
Why shouldn't the strcpy (char *strDestination.char*strSource) be used?
By using this statement:
If (strlen(input) < sizeof(buf) )
Which unsafe function can you make a bit safer?
True or False?
Sprintf() is a safe function in c++
Strncpy(char*strDestination.char*strSource,Count) is safer than strcpy because it adds a count argument. Why is this still vulnerable to buffer overruns?
What is a safe set of string handling functions?
Visual C++ .NET/GS Options are compiler settings that prevents simple stack overruns by using ______ . This is still vulnerable to ______ stack overruns