<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Network Boundaries on Nalar</title>
    <link>https://nalar.dev/tags/network-boundaries/</link>
    <description>Recent content in Network Boundaries on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/network-boundaries/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>DNS Rebinding Preserves Web Origin While the Network Destination Changes</title>
      <link>https://nalar.dev/dns-rebinding-preserves-web-origin-while-the-network-destination-changes/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/dns-rebinding-preserves-web-origin-while-the-network-destination-changes/</guid>
      <description>&lt;h1 id=&#34;dns-rebinding-preserves-web-origin-while-the-network-destination-changes&#34;&gt;DNS Rebinding Preserves Web Origin While the Network Destination Changes&lt;/h1&gt;&#xA;&lt;p&gt;A browser can treat two requests as same-origin even when the TCP connections behind them terminate at different IP addresses. The origin model is built from the URL scheme, host, and port. DNS resolution is a network operation beneath that identity. If a hostname resolves to one address and later resolves to another, the browser-facing origin can remain unchanged.&lt;/p&gt;&#xA;&lt;p&gt;DNS rebinding exploits that separation. An attacker-controlled hostname can initially resolve to an attacker-controlled server that delivers script, then later resolve to an address reachable from the victim&amp;rsquo;s network. Subject to browser, resolver, transport, and target-service behavior, subsequent requests for the same hostname can then cross a network boundary without becoming cross-origin in the browser&amp;rsquo;s origin model.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
