An analysis of binary explotation memory corruption vulnerabilities.
-
Updated
May 12, 2024 - Jupyter Notebook
An analysis of binary explotation memory corruption vulnerabilities.
Some of my Binary Exploitation Write-Ups
HackSys Extreme Vulnerable Driver (HEVD) - Windows & Linux
Paracosme is a zero-click remote memory corruption exploit that compromises ICONICS Genesis64 which was demonstrated successfully on stage during the Pwn2Own Miami 2022 competition.
Explore the depths of stack memory management, from basic concepts to algorithms governing procedure calls/returns, all articulated through comprehensive guides.
Writeups of some of the Binary Exploitation challenges that I have solved during CTF.
Demo project & blog post to demonstrate the use of build schemes in Xcode, diagnosing memory corruption and crashes, sanitizers, analyzing crash logs and symbolication.
A Unit-Based Symbolic Execution Method for Detecting Memory Corruption Vulnerabilities in Executable Codes
A Unit-Based Symbolic Execution Method for Detecting Memory Corruption Vulnerabilities in Executable Codes
Writeups and solver scripts wrote for CTFS and Wargames, mostly memory corruption and reverse engineering tasks.
PoC exploits against various SGX enclaves
Zenith exploits a memory corruption vulnerability in the NetUSB driver to get remote-code execution on the TP-Link Archer C7 V5 router for Pwn2Own Austin 2021.
PoC for CVE-2022-28281 a Mozilla Firefox Out of bounds write.
PoC for CVE-2022-21971 "Windows Runtime Remote Code Execution Vulnerability"
PoC for CVE-2022-21974 "Roaming Security Rights Management Services Remote Code Execution Vulnerability"
Advanced buffer overflow and memory corruption security challenges
A mock (awful) ctf built to practice binary exploitation
Traditional Mitigation in GCC to defend Memory Corruption Vulnerability
Buffer Overflow in Seattle Lab Mail (SLmail) 5.5 - POP3
Add a description, image, and links to the memory-corruption topic page so that developers can more easily learn about it.
To associate your repository with the memory-corruption topic, visit your repo's landing page and select "manage topics."