Content and structure
This commit is contained in:
parent
2a030f2f93
commit
133d7badd9
BIN
work/01paper.pdf
BIN
work/01paper.pdf
Binary file not shown.
@ -77,6 +77,8 @@ vulnerabilities or at least application crashes.
|
||||
|
||||
\subsection{Background}\label{ref:background}
|
||||
|
||||
\subsubsection{Technical Details}
|
||||
|
||||
Exploitation of buffer overflow vulnerabilities almost always works by
|
||||
overriding the return address in the current stack frame, so when the `ret`
|
||||
instruction is executed, an attacker controlled address is moved into the
|
||||
@ -86,6 +88,8 @@ that, if a linked function is called, an attacker controlled function is called
|
||||
instead, or (in C++) overriding the vtable where the pointers to an object's
|
||||
methods are stored.
|
||||
|
||||
\subsubsection{Implications}
|
||||
|
||||
\subsection{Concept and Methods}\label{ref:concept}
|
||||
|
||||
\subsubsection{Runtime Bounds Checks}
|
||||
@ -153,9 +157,13 @@ circumvent the w\^{}x protection.
|
||||
|
||||
\subsubsection{Ineffective or Inefficient}
|
||||
|
||||
Methods that have been shown to be ineffective (e.g. can be circumvented easily)
|
||||
or inefficient (to much runtime overhead)...
|
||||
|
||||
\subsubsection{State of the Art}
|
||||
|
||||
text
|
||||
What techniques are currently used?
|
||||
|
||||
|
||||
\section{Conclusion and Outlook}\label{ref:conclusion}
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user