<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ghidra on binreaper</title>
    <link>https://binreaper.pages.dev/tags/ghidra/</link>
    <description>Recent content in Ghidra on binreaper</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 13 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://binreaper.pages.dev/tags/ghidra/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Born Insecure: What Firmware Analysis Reveals About IoT Security Debt</title>
      <link>https://binreaper.pages.dev/posts/2026-03-13-born-insecure/</link>
      <pubDate>Fri, 13 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://binreaper.pages.dev/posts/2026-03-13-born-insecure/</guid>
      <description>&lt;p&gt;I spent several weeks analyzing the firmware and cloud communication protocol of a popular consumer WiFi camera line. Seven firmware images across six models spanning five years of production — from late 2019 through November 2024.&lt;/p&gt;&#xA;&lt;p&gt;What I found wasn&amp;rsquo;t the kind of vulnerability that gets introduced by a bad commit or fixed in a patch Tuesday. These are architectural decisions made early in the product&amp;rsquo;s life that propagated unchanged across every model, every revision, every year. Shared cryptographic keys with trivially guessable passphrases. A plaintext cloud signaling channel with no integrity protection. An internal command execution daemon that pipes unsanitized input straight into &lt;code&gt;system()&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
