Skip to content

Commit 13f99d1

Browse files
committed
Minor changes
1 parent ae0cee5 commit 13f99d1

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

buffer_overflow/README.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,9 @@
11
# Buffer Overflow
22

3+
### Video (watch after reading)
4+
5+
https://youtu.be/oS2O75H57qU
6+
37
### Overview
48

59
One of the simplest "pwn" attacks is a buffer overflow. The idea is that a faulty program has allocated a buffer of a certain size, but allows you to write more than that size.
@@ -18,6 +22,8 @@ Okay wait up. There are others who can explain the stack way better than I, chec
1822

1923
Philosophical sidetrack - It is okay if things are confusing at this point, that is a lot of security. Just let it settle in and come back to it a little bit every day.
2024

25+
### Attacking
26+
2127
Let's extract out what is important. This is what is stored on a stack frame:
2228

2329
- Local variables
@@ -31,3 +37,5 @@ The return address is also on the stack. What does that mean? Well a function ha
3137
Right now a bell should be going off, look at the diagram again. The stack grows downwards (remember), so we can write past our buffer and overwrite the return address! We can tell the computer where to go next. This is the basic idea of a buffer overflow.
3238

3339
Notice how we attacked. We enumerated every resource that we controlled and figured out how they all interacted with the system. Keep this idea in mind.
40+
41+
### Solution

0 commit comments

Comments
 (0)