Amazing video!! It really takes away the fear of this topic. This explains perfectly that you should not learn all those techniques. You should try to understand how exploitations works in general. Keep it up LiveOverflow ;)
Bravo 👏 this is a masterclass. It took me about 25 minutes to finish the video because I kept rewinding it to understand some concepts and I still have some question which I have to look into but I'm way to tired right now; regardless of that I felt I had to take the time to congratulate you on this piece of art. Thanks for sharing so much knowledge 🙏
as matter of fact this is actually one of the more informative videos - this is actual knowledge, other videos are more of "you can do like this or that". keep up man :D
Great video as always.About time someone made a video on this one.This is why we spend countless hours on debugging/analysis, so we can finally develop that intuition/aptitude.
Before watching this video i was also scared of binary exploitation and now i have a thought that i can somehow learn it. Thank you LiveOverflow. Happy Hacking!!!
@liveoverflow thanks for the video it was really helpful we learned a lot but when are you planning to do another advanced series introducing new way of hacking in the modern world it maybe helpful or maybe just a reference so that i can do it myself to see how much i have improved in binary exploitation
It really clicked for me when I wrote a bootloader, and realised THE STACK WAS OVERWRITING IT, and found out the stack, heap, and code are all in the same place, RAM.
Awesome video once again by LiveOverflow. You are amazing. Really love watching your videos. The are very informative. Thanks man, and I respect your dedication and hard work.
Thanks for that Great simplified explanation. I think what i would like to see is how you would go about seeing what is being written and read from memory. Is there a specific program you use? Or is it brute-force until it works?
I think here's when a debugger comes in. You can stop a program's execution and then examine the memory using a debugger in order to see what's written or changed.
You explained just the right thing ! Great video. I would like to know how multiple programs can use stack at the same time. How do multi- processing and stack work interactively ?
10.52 what??? not useful information??? Man u r kidding. It has to be the first video on this playlist. Can you imagine how it was difficult to understand when u were using something like EIP, EBP and so on. I had to stop the video and go to search for that stuff and then come back. Thanks for your videos, I really appreciate it. Peace.
For me little techniques are difficult like sending interrupt after executed system() or sending binary over ssh after password authentication. Where did you get those knowledge?
For me it was the complete opposite, this video was easy but his other videos flew over my head but probably because I once tried to write a bootloader and a tiny os using assembly, but never used the tools he uses on linux (sorry everybody, I am a widows user)
thank you so much. Please what is the recommended resources for absolute beginners to learn assembly language of Intel x86, and learn binary exploitation?
one thing i am not able to understand that in most operating systems an stack may not have a contiguous block of memory in physical ram. in that can how can a overflow attack can work ?
we don't care about where the stuff is in real memory. If it's in RAM or swapped on disk, or if monkeys write it on papers. Our programs operate on virtual memory and that looks like continuous block of memory. The kernel and hardware makes sure to abstract away the true underlaying physics for us.
let's say for example the value of ebp and esp for stack is 0x100 and 0x96 and return address is at 0x104 so if i have to overwrite the return address then i will have to supply 12bytes of data insted of 4. but if my return address is mapped to 0x1000 in the actual physical address and esp is to 0x2000 then how can someone able to overwrite the return address with only 12 bytes of payload when the actual difference in memory for them is 1000 bytes?
like I said. We don't care about the actual physical RAM address. no program ever deals with ram directly. We have absolutely no idea what the real address is. All you deal with is the virtual memory space... A part of the CPU, the Memory management unit, translates the virtual address to real address. even if we knew the real RAM address, we could never access it. Our programs never use real addresses. all we do is use virtual addresses, so 0x100. and the MMU will translate it on hardware to 0x2000. we never ever see the real address.
I'm wondering if it is enough to exploit real world application i mean sure i know how to exploit vulns but what do you do when there just isn't a vuln, that's kinda what i'm wondering
10:37 XD XD XD Translate Simplified Chinese to English, Or just use English in google translate ;) I know English is not your native language, but i found this quite funny :3 fung sh-way fung -like [func]tion - but g sound instead of c schway [sch] kind of like [sh]eep way, as is.
![[ TEASER ] เงาะป่า - วงL.กฮ. | TMG RECORD](http://i.ytimg.com/vi/M4ObdFfcPww/mqdefault.jpg)
Amazing video!! It really takes away the fear of this topic. This explains perfectly that you should not learn all those techniques. You should try to understand how exploitations works in general. Keep it up LiveOverflow ;)
Bravo 👏 this is a masterclass. It took me about 25 minutes to finish the video because I kept rewinding it to understand some concepts and I still have some question which I have to look into but I'm way to tired right now; regardless of that I felt I had to take the time to congratulate you on this piece of art.
Thanks for sharing so much knowledge 🙏
as matter of fact this is actually one of the more informative videos - this is actual knowledge, other videos are more of "you can do like this or that". keep up man :D
I've been looking for this kind of summary for 2 months now. Great work, thank you!
Great video as always.About time someone made a video on this one.This is why we spend countless hours on debugging/analysis, so we can finally develop that intuition/aptitude.
Lost it at the DHMIS reference. Masterful.
Finally somebody that explains the Why behind the What! Great video!
Your videos were always amazing, but they're still somehow getting even better. Please don't ever stop doing them
I never understood binary exploitation before but i now know whats behind the scenes Thanks LiveOverflow
Before watching this video i was also scared of binary exploitation and now i have a thought that i can somehow learn it. Thank you LiveOverflow. Happy Hacking!!!
Learning to write Shellcode, this is exactly what I needed to hear !
Amazing, as always!
@liveoverflow thanks for the video it was really helpful we learned a lot but when are you planning to do another advanced series introducing new way of hacking in the modern world it maybe helpful or maybe just a reference so that i can do it myself to see how much i have improved in binary exploitation
This first time I know the concept of binary exploitation, thanks!
It really clicked for me when I wrote a bootloader, and realised THE STACK WAS OVERWRITING IT, and found out the stack, heap, and code are all in the same place, RAM.
Awesome video once again by LiveOverflow. You are amazing. Really love watching your videos. The are very informative. Thanks man, and I respect your dedication and hard work.
For some reason, render of the Premiere Pro was just the record. Anyway reuploaded it, thanks for telling :)
yep
Codeinstein
Why did you stop uploading
This should be the first video in the series
Thanks for that Great simplified explanation. I think what i would like to see is how you would go about seeing what is being written and read from memory. Is there a specific program you use? Or is it brute-force until it works?
I think here's when a debugger comes in. You can stop a program's execution and then examine the memory using a debugger in order to see what's written or changed.
You explained just the right thing ! Great video.
I would like to know how multiple programs can use stack at the same time. How do multi- processing and stack work interactively ?
Every process has their own stacks inside of their virtual address space and they never interact.
Thats overflowed my memory
lol
Where did you find that Elf walkthrough graphic? That looks really helpful, would be nice to have as an image.
(Talking about 4:10)
search for corkami's github. it's part of a series of file formats diagrams
Amazing! Thank you!!!❤❤
Thanks for making these videos, they cheer me up everytime!
Thumbs up man ! Great work, especially the impressive quality of the presentation :)
Really interested.
Thanks you alot!!!
Waiting your next tutorial
this is very good awesome and very creative , now i understand more and more and more , i loved it please MORE .
10.52 what??? not useful information??? Man u r kidding. It has to be the first video on this playlist. Can you imagine how it was difficult to understand when u were using something like EIP, EBP and so on. I had to stop the video and go to search for that stuff and then come back. Thanks for your videos, I really appreciate it. Peace.
Do you have some artist background ? I mean all your videos are well illustrated and it's cool :D
+Rastakiwi Roubal lol no. Tracing a lot of stuff
This is amazing. Thank you for your pro educational efforts.
Exactly what I wanted to see. Great :)
Thanks
My favorite episode, "bin "
6:27 Not exactly - ESP dictates where the top of the stack is, so if it points in the middle of your code section then this is where the stack is.
+Agnus Xendis that's basically what I said. No?
2:18 0x3 points to the 3rd instruction? Shouldn't it oint to the 4th, because 0x0 is first 0x1 is second 0x2 is third 0x3 is fourth? I am confused.
Awesome video. Greatly explained
For me little techniques are difficult like sending interrupt after executed system() or sending binary over ssh after password authentication. Where did you get those knowledge?
Any plans for solving crackme? ARM or any other arch like MIPS
.
Thanks for these videos :) great content and easy to understand. Great Job!!
It made sense; Thought I still feel it's over my head
For me it was the complete opposite, this video was easy but his other videos flew over my head
but probably because I once tried to write a bootloader and a tiny os using assembly, but never used the tools he uses on linux (sorry everybody, I am a widows user)
Come to the not-darkside
super cool! Thank you!
thanks for this video
Your content is so awesome that one video per week is not enough. Let me be selfish and suggest you should go back to 2 videos per week :).
Please more videos like this or learning resources. Please /\
Thanks a lot for such amazing videos.
thank you so much.
Please what is the recommended resources for absolute beginners to learn assembly language of Intel x86, and learn binary exploitation?
opensecuritytraining lectures are good.
liked it, also good job with all these images =)
Awesome job! Keep it up!
one thing i am not able to understand that in most operating systems an stack may not have a contiguous block of memory in physical ram. in that can how can a overflow attack can work ?
we don't care about where the stuff is in real memory. If it's in RAM or swapped on disk, or if monkeys write it on papers. Our programs operate on virtual memory and that looks like continuous block of memory. The kernel and hardware makes sure to abstract away the true underlaying physics for us.
let's say for example the value of ebp and esp for stack is 0x100 and 0x96 and return address is at 0x104 so if i have to overwrite the return address then i will have to supply 12bytes of data insted of 4. but if my return address is mapped to 0x1000 in the actual physical address and esp is to 0x2000 then how can someone able to overwrite the return address with only 12 bytes of payload when the actual difference in memory for them is 1000 bytes?
like I said. We don't care about the actual physical RAM address. no program ever deals with ram directly. We have absolutely no idea what the real address is. All you deal with is the virtual memory space... A part of the CPU, the Memory management unit, translates the virtual address to real address.
even if we knew the real RAM address, we could never access it. Our programs never use real addresses.
all we do is use virtual addresses, so 0x100. and the MMU will translate it on hardware to 0x2000. we never ever see the real address.
thanks for the reply.
This all went above from my head😂😂
Has anyone ever made a hack to stop bullets in mid air???
This video had not got near enough love
This is so good!
I'm wondering if it is enough to exploit real world application
i mean sure i know how to exploit vulns
but what do you do when there just isn't a vuln, that's kinda what i'm wondering
when there is no vuln, there is no vuln :P
Rip
Real hacker , will find a vul
Awesome vid dude
So in a buffer overflow nothing overflows ?
eh? The buffer overflows
LiveOverflow oh understand now . I though you just wrote on a single address , the top of the stack .
great video!!
Where i can get the image at 4:20 ?
ih1.redbubble.net/image.15341732.6212/flat,800x800,070,f.u1.jpg
"Well defined, deterministic" ... okay okay lets not get too crazy here lol
10:37 XD XD XD
Translate Simplified Chinese to English, Or just use English in google translate ;) I know English is not your native language, but i found this quite funny :3
fung sh-way
fung -like [func]tion - but g sound instead of c
schway
[sch] kind of like [sh]eep
way, as is.
cool
This remembers me to the time where i manage to develop my first exploit for SLmail.exe :b In Terms of achieving my OSCP Certification!
its again become un-understand able thing
Channels like this shouldn't be public , else we won't be able to flex 😂
Wrong mindset, bro!
German accent
Great content as usual! thanks for spending so much time on creating great content and sharing with the community.