<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Binary Exploitation on RGROSEC</title><link>https://aegrah.github.io/categories/binary-exploitation.html</link><description>Recent content in Binary Exploitation on RGROSEC</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © Ruben Groenewoud</copyright><lastBuildDate>Mon, 25 Apr 2022 13:33:38 +0200</lastBuildDate><atom:link href="https://aegrah.github.io/categories/binary-exploitation/index.xml" rel="self" type="application/rss+xml"/><item><title>x86 Stack-Based Windows Buffer Overflow - Pt. 2</title><link>https://aegrah.github.io/post/2022-02-25-x86-windows-buffer-overflow-pt2.html</link><pubDate>Mon, 25 Apr 2022 13:33:38 +0200</pubDate><guid>https://aegrah.github.io/post/2022-02-25-x86-windows-buffer-overflow-pt2.html</guid><description>
This tutorial is part two of a two part series that focuses on binary exploitation, in particular on x86 stack-based Windows buffer overflows. The first part of the series focuses on the theory behind the topics that will be described in this tutorial, and can be found here. The information provided in this blog is based on the notes and cheatsheets I wrote while studying for the Offensive Security Certified Professional (OSCP) exam.</description></item><item><title>x86 Stack-Based Windows Buffer Overflow - Pt. 1</title><link>https://aegrah.github.io/post/2022-02-25-x86-windows-buffer-overflow-pt1.html</link><pubDate>Mon, 25 Apr 2022 13:33:35 +0200</pubDate><guid>https://aegrah.github.io/post/2022-02-25-x86-windows-buffer-overflow-pt1.html</guid><description>
This tutorial is part one of a two part series that focuses on binary exploitation, in particular on x86 stack-based Windows buffer overflows. This part of the series focuses on the theory behind memory, processors and buffer overflows. We first take a look at some simple c programs and assembly, then dive into the different memory regions and how processes are executed. We then take a look at a vulnerable program in a debugger to see what a buffer overflow looks like.</description></item></channel></rss>