<?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: TCP Source Port Pass Firewall Vulnerability in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/tcp-source-port-pass-firewall-vulnerability/m-p/478468#M103763</link>
    <description>&lt;P&gt;Make sure that all your filtering rules are correct and strict enough. If the&lt;BR /&gt;firewall intends to deny TCP connections to a specific port, it should be&lt;BR /&gt;configured to block all TCP SYN packets going to this port, regardless of the&lt;BR /&gt;source port.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have you configured the FW to utilize PANW best practices for Zone and Dos Protections?&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/best-practices/10-0/dos-and-zone-protection-best-practices" target="_blank"&gt;https://docs.paloaltonetworks.com/best-practices/10-0/dos-and-zone-protection-best-practices&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 05 Apr 2022 20:05:15 GMT</pubDate>
    <dc:creator>S.Cantwell</dc:creator>
    <dc:date>2022-04-05T20:05:15Z</dc:date>
    <item>
      <title>TCP Source Port Pass Firewall Vulnerability</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/tcp-source-port-pass-firewall-vulnerability/m-p/477874#M103706</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are getting below vulnerability in PA NGFW.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please find the error below,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;TABLE width="1664"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="64"&gt;IP Status&lt;/TD&gt;&lt;TD width="64"&gt;QID&lt;/TD&gt;&lt;TD width="64"&gt;Title&lt;/TD&gt;&lt;TD width="64"&gt;Type&lt;/TD&gt;&lt;TD width="64"&gt;Severity&lt;/TD&gt;&lt;TD width="64"&gt;Port&lt;/TD&gt;&lt;TD width="64"&gt;Protocol&lt;/TD&gt;&lt;TD width="64"&gt;FQDN&lt;/TD&gt;&lt;TD width="64"&gt;SSL&lt;/TD&gt;&lt;TD width="64"&gt;CVE ID&lt;/TD&gt;&lt;TD width="64"&gt;Vendor Reference&lt;/TD&gt;&lt;TD width="64"&gt;Bugtraq ID&lt;/TD&gt;&lt;TD width="64"&gt;CVSS Base&lt;/TD&gt;&lt;TD width="64"&gt;CVSS Temporal&lt;/TD&gt;&lt;TD width="64"&gt;CVSS3 Base&lt;/TD&gt;&lt;TD width="64"&gt;CVSS3 Temporal&lt;/TD&gt;&lt;TD width="64"&gt;Threat&lt;/TD&gt;&lt;TD width="64"&gt;Impact&lt;/TD&gt;&lt;TD width="64"&gt;Solution&lt;/TD&gt;&lt;TD width="64"&gt;Exploitability&lt;/TD&gt;&lt;TD width="64"&gt;Associated Malware&lt;/TD&gt;&lt;TD width="64"&gt;Results&lt;/TD&gt;&lt;TD width="64"&gt;PCI Vuln&lt;/TD&gt;&lt;TD width="64"&gt;Instance&lt;/TD&gt;&lt;TD width="64"&gt;Category&lt;/TD&gt;&lt;TD width="64"&gt;Result Errors&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;host scanned, found vuln&lt;/TD&gt;&lt;TD&gt;34000&lt;/TD&gt;&lt;TD&gt;TCP Source Port Pass Firewall&lt;/TD&gt;&lt;TD&gt;Vuln&lt;/TD&gt;&lt;TD&gt;3&lt;/TD&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;5.0 (AV:N/AC:L/Au:N/C:P/I:N/A:N)&lt;/TD&gt;&lt;TD&gt;3.6 (E:U/RL:W/RC:UC)&lt;/TD&gt;&lt;TD&gt;Your firewall policy seems to let TCP packets with a specific source port pass through.&lt;/TD&gt;&lt;TD&gt;Some types of requests can pass through the firewall. The port number listed in the results section of this vulnerability report is the source port that unauthorized users can use to bypass your firewall.&lt;/TD&gt;&lt;TD&gt;Make sure that all your filtering rules are correct and strict enough. If the firewall intends to deny TCP connections to a specific port, it should be configured to block all TCP SYN packets going to this port, regardless of the source port.&lt;/TD&gt;&lt;TD&gt;The host responded 4 times to 4 TCP SYN probes sent to destination port 25 using source port 25. However, it did not respond at all to 4 TCP SYN probes sent to the same destination port using a random source port.&lt;/TD&gt;&lt;TD&gt;yes&lt;/TD&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;Firewall&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
      <pubDate>Mon, 04 Apr 2022 08:10:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/tcp-source-port-pass-firewall-vulnerability/m-p/477874#M103706</guid>
      <dc:creator>SubaMuthuram</dc:creator>
      <dc:date>2022-04-04T08:10:08Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Source Port Pass Firewall Vulnerability</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/tcp-source-port-pass-firewall-vulnerability/m-p/478468#M103763</link>
      <description>&lt;P&gt;Make sure that all your filtering rules are correct and strict enough. If the&lt;BR /&gt;firewall intends to deny TCP connections to a specific port, it should be&lt;BR /&gt;configured to block all TCP SYN packets going to this port, regardless of the&lt;BR /&gt;source port.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have you configured the FW to utilize PANW best practices for Zone and Dos Protections?&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/best-practices/10-0/dos-and-zone-protection-best-practices" target="_blank"&gt;https://docs.paloaltonetworks.com/best-practices/10-0/dos-and-zone-protection-best-practices&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Apr 2022 20:05:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/tcp-source-port-pass-firewall-vulnerability/m-p/478468#M103763</guid>
      <dc:creator>S.Cantwell</dc:creator>
      <dc:date>2022-04-05T20:05:15Z</dc:date>
    </item>
  </channel>
</rss>

