<?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: CVE-2023-38802 in Advanced Threat Prevention Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/cve-2023-38802/m-p/557847#M1998</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/167427"&gt;@securehops&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;this issue is triggered by sending crafted BGP update message. If you are running BGP internally within your network only and all your BGP devices are in your control, then I would say you are not affected (Unless somebody you are peering internally sends malicious BGP update).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This issue is not limited to Palo Alto only. End of last month similar issue was reported by Juniper&amp;nbsp;&lt;A href="https://supportportal.juniper.net/s/article/2023-08-29-Out-of-Cycle-Security-Bulletin-Junos-OS-and-Junos-OS-Evolved-A-crafted-BGP-UPDATE-message-allows-a-remote-attacker-to-de-peer-reset-BGP-sessions-CVE-2023-4481?language=en_US" target="_self"&gt;CVE-2023-4481&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kind Regards&lt;/P&gt;
&lt;P&gt;Pavel&lt;/P&gt;</description>
    <pubDate>Thu, 14 Sep 2023 04:17:57 GMT</pubDate>
    <dc:creator>PavelK</dc:creator>
    <dc:date>2023-09-14T04:17:57Z</dc:date>
    <item>
      <title>CVE-2023-38802</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/cve-2023-38802/m-p/557820#M1997</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regarding CVE-2023-38802, DDOS in BGP software,&amp;nbsp; would this apply only to public ASNs/BGP sessions established on public internet?&amp;nbsp; &amp;nbsp;I have BGP configured on PAN firewalls but only running BGP over IPSec tunnels using private ASNs&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would think this vulnerability would not apply but didn't want to assume&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://security.paloaltonetworks.com/CVE-2023-38802" target="_blank"&gt;https://security.paloaltonetworks.com/CVE-2023-38802&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Sep 2023 01:21:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/cve-2023-38802/m-p/557820#M1997</guid>
      <dc:creator>securehops</dc:creator>
      <dc:date>2023-09-14T01:21:22Z</dc:date>
    </item>
    <item>
      <title>Re: CVE-2023-38802</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/cve-2023-38802/m-p/557847#M1998</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/167427"&gt;@securehops&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;this issue is triggered by sending crafted BGP update message. If you are running BGP internally within your network only and all your BGP devices are in your control, then I would say you are not affected (Unless somebody you are peering internally sends malicious BGP update).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This issue is not limited to Palo Alto only. End of last month similar issue was reported by Juniper&amp;nbsp;&lt;A href="https://supportportal.juniper.net/s/article/2023-08-29-Out-of-Cycle-Security-Bulletin-Junos-OS-and-Junos-OS-Evolved-A-crafted-BGP-UPDATE-message-allows-a-remote-attacker-to-de-peer-reset-BGP-sessions-CVE-2023-4481?language=en_US" target="_self"&gt;CVE-2023-4481&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kind Regards&lt;/P&gt;
&lt;P&gt;Pavel&lt;/P&gt;</description>
      <pubDate>Thu, 14 Sep 2023 04:17:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/cve-2023-38802/m-p/557847#M1998</guid>
      <dc:creator>PavelK</dc:creator>
      <dc:date>2023-09-14T04:17:57Z</dc:date>
    </item>
    <item>
      <title>Re: CVE-2023-38802</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/cve-2023-38802/m-p/565399#M2059</link>
      <description>&lt;P&gt;Any reason it says it is fixed in 11.0.3 (&lt;A href="https://security.paloaltonetworks.com/CVE-2023-38802" target="_blank" rel="nofollow noopener noreferrer"&gt;https://security.paloaltonetworks.com/CVE-2023-38802&lt;/A&gt;), but the 11.0.3 known and addressed issues does not show it?&lt;/P&gt;</description>
      <pubDate>Mon, 13 Nov 2023 18:56:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/cve-2023-38802/m-p/565399#M2059</guid>
      <dc:creator>knuanes</dc:creator>
      <dc:date>2023-11-13T18:56:45Z</dc:date>
    </item>
    <item>
      <title>Re: CVE-2023-38802</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/cve-2023-38802/m-p/565417#M2060</link>
      <description>&lt;P&gt;11.0.3 is not impacted.&amp;nbsp; &amp;nbsp;The impacted versions are &amp;lt; 11.0.3&lt;/P&gt;</description>
      <pubDate>Mon, 13 Nov 2023 22:00:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/cve-2023-38802/m-p/565417#M2060</guid>
      <dc:creator>securehops</dc:creator>
      <dc:date>2023-11-13T22:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: CVE-2023-38802</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/cve-2023-38802/m-p/565418#M2061</link>
      <description>&lt;P&gt;For any drive-by browsers, you can secure your BGP connections only to/from specific IP addresses with an allow security policy rule followed by a drop rule.&amp;nbsp; Then your NGFW will only allow BGP packets from configured peers.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tom&lt;/P&gt;</description>
      <pubDate>Mon, 13 Nov 2023 22:05:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/cve-2023-38802/m-p/565418#M2061</guid>
      <dc:creator>TomYoung</dc:creator>
      <dc:date>2023-11-13T22:05:09Z</dc:date>
    </item>
    <item>
      <title>Re: CVE-2023-38802</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/cve-2023-38802/m-p/565420#M2062</link>
      <description>&lt;P&gt;Thanks, yes the release notes "usually" state that the issue was addressed. In this case it does not. We are on 11.0.2, an affected ver and want to move to 11.0.3, the not impacted ver. But first want to confirm on the release notes that it was a fixed addressed issue.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Nov 2023 22:06:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/cve-2023-38802/m-p/565420#M2062</guid>
      <dc:creator>knuanes</dc:creator>
      <dc:date>2023-11-13T22:06:21Z</dc:date>
    </item>
    <item>
      <title>Re: CVE-2023-38802</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/cve-2023-38802/m-p/565421#M2063</link>
      <description>&lt;P&gt;true, good point.&amp;nbsp; They had so many addressed issues in 11.0.3, they forgot that one&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":face_with_tears_of_joy:"&gt;😂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Nov 2023 22:14:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/cve-2023-38802/m-p/565421#M2063</guid>
      <dc:creator>securehops</dc:creator>
      <dc:date>2023-11-13T22:14:50Z</dc:date>
    </item>
  </channel>
</rss>

