<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Exploit-Development on HackingPassion.com : root@HackingPassion.com-[~]</title><link>https://hackingpassion.com/tags/exploit-development/</link><description>Recent content in Exploit-Development on HackingPassion.com : root@HackingPassion.com-[~]</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 05 Jun 2026 09:58:54 +0200</lastBuildDate><atom:link href="https://hackingpassion.com/tags/exploit-development/index.xml" rel="self" type="application/rss+xml"/><item><title>Watch a Buffer Overflow Take Over a Machine on Your Own Lab</title><link>https://hackingpassion.com/buffer-overflow-explained/</link><pubDate>Fri, 05 Jun 2026 09:58:54 +0200</pubDate><guid>https://hackingpassion.com/buffer-overflow-explained/</guid><description>&lt;h1 id="buffer-overflows-the-oldest-way-to-take-over-a-machine-and-how-to-see-it-work-on-your-own-lab">Buffer Overflows: The Oldest Way to Take Over a Machine, and How to See It Work on Your Own Lab&lt;/h1>
&lt;p>Give a running program more data than it was built to hold, and on a lot of systems that extra data does not just get thrown away. It spills into the memory right next to it. And with a little care, that spilled data ends up running as code, with full control over the machine.&lt;/p></description></item></channel></rss>