<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Iot on binreaper</title>
    <link>https://binreaper.pages.dev/tags/iot/</link>
    <description>Recent content in Iot 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/iot/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>
    <item>
      <title>HTB CCTV — ZoneMinder SQLi to Root via motionEye Signed API Command Injection</title>
      <link>https://binreaper.pages.dev/posts/2026-03-09-htb-cctv/</link>
      <pubDate>Mon, 09 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://binreaper.pages.dev/posts/2026-03-09-htb-cctv/</guid>
      <description>&lt;h2 id=&#34;tldr&#34;&gt;TL;DR&lt;/h2&gt;&#xA;&lt;p&gt;Log into ZoneMinder with default credentials (&lt;code&gt;admin:admin&lt;/code&gt;), use CVE-2024-51482 (SQL injection) to extract the bcrypt password hash for user &lt;code&gt;mark&lt;/code&gt;, crack it (&lt;code&gt;opensesame&lt;/code&gt;), SSH in, then exploit motionEye (running as root on localhost:8765) by forging HMAC-signed API requests using the admin password hash from the config file to inject a command into the &lt;code&gt;on_event_start&lt;/code&gt; hook, and trigger it via the motion HTTP control API.&lt;/p&gt;&#xA;&lt;h2 id=&#34;enumeration&#34;&gt;Enumeration&lt;/h2&gt;&#xA;&lt;h3 id=&#34;port-scan&#34;&gt;Port Scan&lt;/h3&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-fallback&#34; data-lang=&#34;fallback&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;22/tcp — OpenSSH 9.6p1 Ubuntu&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;80/tcp — Apache 2.4.58 (Ubuntu) → redirects to http://cctv.htb/&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Add &lt;code&gt;cctv.htb&lt;/code&gt; to &lt;code&gt;/etc/hosts&lt;/code&gt; and browse to port 80.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cracking Passwords from Embedded Linux Devices: The musl DES Crypt $ Salt Problem</title>
      <link>https://binreaper.pages.dev/posts/2026-03-04-musl-des-crypt-salt/</link>
      <pubDate>Wed, 04 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://binreaper.pages.dev/posts/2026-03-04-musl-des-crypt-salt/</guid>
      <description>&lt;p&gt;When extracting &lt;code&gt;/etc/shadow&lt;/code&gt; from embedded Linux devices — routers, IoT gateways, cameras — you&amp;rsquo;ll occasionally encounter password hashes that every standard cracking tool refuses to touch. Not because the hash is strong, but because the C library that generated it plays by slightly different rules.&lt;/p&gt;&#xA;&lt;p&gt;This post documents a specific case: DES crypt hashes with a &lt;code&gt;$&lt;/code&gt; character in the salt, generated by musl libc on an OpenWrt-based router. The fix is a one-character substitution that makes the hash crackable in seconds.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
