<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Exploit Intel — gdb</title><link>https://exploit-intel.com/blog/tags/gdb/</link><description>EIP research articles tagged gdb.</description><language>en-us</language><atom:link href="https://exploit-intel.com/blog/tags/gdb/index.xml" rel="self" type="application/rss+xml"/><lastBuildDate>Wed, 04 Mar 2026 22:00:00 -0400</lastBuildDate><item><title>CVE-2025-68670 Part 2: From Crash to RCE - The One That Fought Back (and Lost)</title><link>https://exploit-intel.com/blog/posts/cve-2025-68670-xrdp-from-crash-to-rce-the-one-that-fought-back/</link><guid isPermaLink="true">https://exploit-intel.com/blog/posts/cve-2025-68670-xrdp-from-crash-to-rce-the-one-that-fought-back/</guid><description>The first post ended with 'not a shell.' This one ends with uid=0(root) - with an asterisk. Ten context windows. A UTF-8 encoding barrier that blocks every libc address. A PLT mapping that lied. A stack alignment problem solved by a NULL pointer and a filename that shouldn't exist. The story of how a pre-auth xrdp overflow became (almost) pure-network RCE - through the most absurd gadget chain we've ever built.</description><pubDate>Wed, 04 Mar 2026 22:00:00 -0400</pubDate></item><item><title>CVE-2025-68670: Pre-Auth xrdp Overflow - The One Where the Protocol Fought Back</title><link>https://exploit-intel.com/blog/posts/cve-2025-68670-xrdp-pre-auth-overflow-the-hard-one/</link><guid isPermaLink="true">https://exploit-intel.com/blog/posts/cve-2025-68670-xrdp-pre-auth-overflow-the-hard-one/</guid><description>xrdp. Pre-authentication. A full RDP handshake implemented from scratch. UTF-8 encoding constraints that break your ROP chain. A false crash path that wasted hours. And a 3-byte partial overwrite technique that reaches any address in the binary. Stackforge's hardest target yet - and the most honest result.</description><pubDate>Wed, 04 Mar 2026 18:00:00 -0400</pubDate></item><item><title>CVE-2025-62507: Redis Stack Overflow to RCE in 68 Minutes  -  Then We Turned ASLR On</title><link>https://exploit-intel.com/blog/posts/cve-2025-62507-redis-stackforge-from-crash-to-rce-with-aslr/</link><guid isPermaLink="true">https://exploit-intel.com/blog/posts/cve-2025-62507-redis-stackforge-from-crash-to-rce-with-aslr/</guid><description>The public material available during this CVE-2025-62507 run was a crash PoC. StackForge pursued RCE, then repeated the work with ASLR enabled.</description><pubDate>Tue, 03 Mar 2026 18:00:00 -0400</pubDate></item><item><title>CVE-2025-15467: From OpenSSL Stack Overflow to Three ROP Chains in 64 Minutes  -  Introducing Stackforge</title><link>https://exploit-intel.com/blog/posts/cve-2025-15467-openssl-stackforge-autonomous-binary-exploit/</link><guid isPermaLink="true">https://exploit-intel.com/blog/posts/cve-2025-15467-openssl-stackforge-autonomous-binary-exploit/</guid><description>We forked Shannon again  -  this time for binary exploit development. Nine AI agents, GDB as an MCP tool, packet capture via SharkMCP, and a pipeline that turned an OpenSSL stack buffer overflow into three independent ROP chains with GDB-verified RCE. Eighty-five minutes. Twenty-five dollars. Here's how Stackforge works.</description><pubDate>Tue, 03 Mar 2026 12:00:00 -0400</pubDate></item></channel></rss>
