<?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>L2-Broadcast on Netacoding | Cybersecurity, Assembly &amp; Network Research</title>
    <link>https://netacoding.com/tags/l2-broadcast/</link>
    <description>Recent content in L2-Broadcast on Netacoding | Cybersecurity, Assembly &amp; Network Research</description>
    <image>
      <title>Netacoding | Cybersecurity, Assembly &amp; Network Research</title>
      <url>https://netacoding.com/img/logo-netacoding.png</url>
      <link>https://netacoding.com/img/logo-netacoding.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 05 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://netacoding.com/tags/l2-broadcast/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Smurf Amplification in 2026: Pre-Auth ICMP Reflection via L2 Broadcast | CVE-1999-0513 &amp; Enterprise VLAN</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 disabled directed broadcast at router level — not L2 broadcast domains. Missing uRPF (CWE-290) &#43; broadcast ICMP reply (CWE-406) enables Smurf amplification from same-VLAN adjacency with no authentication. 100-host broadcast domain = 100x amplification at 100 req/s → 7.2 Mbps victim flood. Two-machine Scapy PoC, Suricata rules, and enterprise wireless infrastructure confirmation.</description>
    </item>
  </channel>
</rss>
