<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: can we  mitigate CVE-2021-3031 PAN-OS by restricting dataplane interfaces of NGFW in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/can-we-mitigate-cve-2021-3031-pan-os-by-restricting-dataplane/m-p/380120#M89643</link>
    <description>&lt;P&gt;the vulnerability only applies to locally conneced hosts (same ethernet subnet), so a workaround would be to remove local subnet connectivity (adding routers)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;upgrading up to the recommended level would probably be a better solution&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 15 Jan 2021 08:48:40 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2021-01-15T08:48:40Z</dc:date>
    <item>
      <title>can we  mitigate CVE-2021-3031 PAN-OS by restricting dataplane interfaces of NGFW</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/can-we-mitigate-cve-2021-3031-pan-os-by-restricting-dataplane/m-p/380093#M89642</link>
      <description>&lt;P&gt;CVE-2021-3031 PAN-OS: Information exposure in Ethernet data frame construction (Etherleak)&lt;/P&gt;&lt;P&gt;Padding bytes in Ethernet packets on PA-200, PA-220, PA-500, PA-800, PA-2000 Series, PA-3000 Series, PA-3200 Series, PA-5200 Series, and PA-7000 Series firewalls are not cleared before the data frame is created. This leaks a small amount of random information from the firewall memory into the Ethernet packets. An attacker on the same Ethernet subnet as the PAN-OS firewall is able to collect potentially sensitive information from these packets.&lt;/P&gt;&lt;P&gt;This issue is also known as Etherleak and is detected by security scanners as CVE-2003-0001.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://security.paloaltonetworks.com/CVE-2021-3031" target="_blank" rel="noopener"&gt;https://security.paloaltonetworks.com/CVE-2021-3031&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Workarounds and Mitigations&lt;/P&gt;&lt;P&gt;There is no workaround to prevent the information leak in the Ethernet packets; however, restricting access to the networks mitigates the risk of this issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This issue fixed in latest software versions , but we need some workaround.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Can we restrict data plane&amp;nbsp;interface access of NGFW as workaround for this security advisory.&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jan 2021 06:52:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/can-we-mitigate-cve-2021-3031-pan-os-by-restricting-dataplane/m-p/380093#M89642</guid>
      <dc:creator>Deepak_K</dc:creator>
      <dc:date>2021-01-15T06:52:01Z</dc:date>
    </item>
    <item>
      <title>Re: can we  mitigate CVE-2021-3031 PAN-OS by restricting dataplane interfaces of NGFW</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/can-we-mitigate-cve-2021-3031-pan-os-by-restricting-dataplane/m-p/380120#M89643</link>
      <description>&lt;P&gt;the vulnerability only applies to locally conneced hosts (same ethernet subnet), so a workaround would be to remove local subnet connectivity (adding routers)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;upgrading up to the recommended level would probably be a better solution&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jan 2021 08:48:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/can-we-mitigate-cve-2021-3031-pan-os-by-restricting-dataplane/m-p/380120#M89643</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2021-01-15T08:48:40Z</dc:date>
    </item>
  </channel>
</rss>

