<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>cyberdream.blog</title>
		<link>https://cyberdream.blog/</link>
		<description>Recent content on cyberdream.blog</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Fri, 07 Aug 2026 11:52:47 +0000</lastBuildDate>
		
			<atom:link href="https://cyberdream.blog/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Heap Exploitation Lab 01 - House of Force</title>
				<link>https://cyberdream.blog/posts/heap-exploitation-lab-01-house-of-force/</link>
				<pubDate>Fri, 07 Aug 2026 11:52:47 +0000</pubDate>
				<guid>https://cyberdream.blog/posts/heap-exploitation-lab-01-house-of-force/</guid>
				<description>&lt;h2 id=&#34;introduction&#34;&gt;&#xA;  Introduction&#xA;  &lt;a class=&#34;heading-link&#34; href=&#34;#introduction&#34;&gt;&#xA;    &lt;i class=&#34;fa-solid fa-link&#34; aria-hidden=&#34;true&#34; title=&#34;Link to heading&#34;&gt;&lt;/i&gt;&#xA;    &lt;span class=&#34;sr-only&#34;&gt;Link to heading&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Most heap exploitation tutorials focus on isolated CTF challenges or a single binary with one bug and a clear path to the flag. Real embedded firmware is different. Vulnerabilities are spread across multiple handlers, exploitation requires chaining several bugs together, and you&amp;rsquo;re working against an allocator with its own quirks and version-specific behaviors.&lt;/p&gt;&#xA;&lt;p&gt;To bridge that gap, I built a practice target from scratch using Claude: a deliberately vulnerable HTTP server modeled after the kind of &lt;code&gt;httpd&lt;/code&gt; daemons found in consumer routers. This post walks through the target design, the vulnerabilities I embedded in it, and the full exploit chain I developed: from information leak to remote code execution using the House of Force technique against glibc 2.23.&lt;/p&gt;</description>
			</item>
			<item>
				<title>D-Link DCS-935l | CVE-2025-10779</title>
				<link>https://cyberdream.blog/posts/d-link-dcs-935l-cve-2025-10779/</link>
				<pubDate>Tue, 30 Jun 2026 17:16:45 +0000</pubDate>
				<guid>https://cyberdream.blog/posts/d-link-dcs-935l-cve-2025-10779/</guid>
				<description>&lt;p&gt;This exploit was developed in EMUX firmware emulation framework where target is build in.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Vulnerability type:&lt;/strong&gt; Stack buffer overflow&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Tested firmware version:&lt;/strong&gt; 1.06&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Exploit mitigations:&lt;/strong&gt; None&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Executable&lt;/strong&gt;: /web/cgi-bin/hnap/hnap_service&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Function reported:&lt;/strong&gt; sub_402280&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Real function&lt;/strong&gt;: sub_401f5c, strcpy at 0x402230&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;tools&#34;&gt;&#xA;  Tools&#xA;  &lt;a class=&#34;heading-link&#34; href=&#34;#tools&#34;&gt;&#xA;    &lt;i class=&#34;fa-solid fa-link&#34; aria-hidden=&#34;true&#34; title=&#34;Link to heading&#34;&gt;&lt;/i&gt;&#xA;    &lt;span class=&#34;sr-only&#34;&gt;Link to heading&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Ubuntu 24.04.4 LTS&#xA;&lt;ul&gt;&#xA;&lt;li&gt;qemu-user-static&lt;/li&gt;&#xA;&lt;li&gt;gcc-mips-linux-gnu&lt;/li&gt;&#xA;&lt;li&gt;binutils-mips-linux-gnu&lt;/li&gt;&#xA;&lt;li&gt;python3-pip&lt;/li&gt;&#xA;&lt;li&gt;python3-venv&lt;/li&gt;&#xA;&lt;li&gt;gdb-multiarch&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;EMUX framework (&lt;a href=&#34;https://github.com/therealsaumil/emux&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;https://github.com/therealsaumil/emux&lt;/a&gt;)&lt;/li&gt;&#xA;&lt;li&gt;Binary Ninja&#xA;&lt;ul&gt;&#xA;&lt;li&gt;VulnFanatic plugin&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;python3&#xA;&lt;ul&gt;&#xA;&lt;li&gt;pwntools&lt;/li&gt;&#xA;&lt;li&gt;requests&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;static mips tools (&lt;a href=&#34;https://github.com/CyberDanube/medusa-embedded-toolkit&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;https://github.com/CyberDanube/medusa-embedded-toolkit&lt;/a&gt;)&#xA;&lt;ul&gt;&#xA;&lt;li&gt;gdbserver&lt;/li&gt;&#xA;&lt;li&gt;strace&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;research&#34;&gt;&#xA;  Research&#xA;  &lt;a class=&#34;heading-link&#34; href=&#34;#research&#34;&gt;&#xA;    &lt;i class=&#34;fa-solid fa-link&#34; aria-hidden=&#34;true&#34; title=&#34;Link to heading&#34;&gt;&lt;/i&gt;&#xA;    &lt;span class=&#34;sr-only&#34;&gt;Link to heading&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;This N-day vulnerability was reported for newer firmware version so we must do research for right vulnerable function. When we search for vulnerable function address &lt;em&gt;0x402280&lt;/em&gt; in Binary Ninja, we land in the middle of function &lt;em&gt;sub_401f5c&lt;/em&gt;.&lt;/p&gt;</description>
			</item>
			<item>
				<title>About me</title>
				<link>https://cyberdream.blog/about/</link>
				<pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate>
				<guid>https://cyberdream.blog/about/</guid>
				<description></description>
			</item>
	</channel>
</rss>
