<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Scapy on Netacoding | Cybersecurity, Assembly &amp; Network Research</title>
    <link>https://netacoding.com/tags/scapy/</link>
    <description>Recent content in Scapy on Netacoding | Cybersecurity, Assembly &amp; Network Research</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 05 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://netacoding.com/tags/scapy/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>EtherLeak: IP Total Length Over-read via Ethernet Frame Padding</title>
      <link>https://netacoding.com/posts/etherleak-reloaded/</link>
      <pubDate>Fri, 05 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://netacoding.com/posts/etherleak-reloaded/</guid>
      <description>IP Total Length over-read through Ethernet padding — CVE-2003-0001 to CVE-2021-3031 and beyond. The mechanism, the math, TTL=0 invisibility, and a working Scapy PoC.</description>
    </item>
    <item>
      <title>Smurf Amplification in 2026: Pre-Auth ICMP Reflection via L2 Broadcast</title>
      <link>https://netacoding.com/posts/smurf-amplification/</link>
      <pubDate>Fri, 05 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://netacoding.com/posts/smurf-amplification/</guid>
      <description>RFC 2644 didn&amp;#39;t kill Smurf — it killed the routed case. L2 broadcast domains, missing uRPF, and pre-auth ICMP reflection keep the 28-year-old mechanism alive in enterprise infrastructure.</description>
    </item>
  </channel>
</rss>
