<?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 How Palo Alto Networks Identifies GnuTLS Server Hello Session ID Heap Buffer Over Without Decryption in Advanced Threat Prevention Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/how-palo-alto-networks-identifies-gnutls-server-hello-session-id/m-p/220109#M357</link>
    <description>&lt;P&gt;HI All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We detected&lt;STRONG&gt; Vulnerability:&lt;/STRONG&gt; 36926 ID- GnuTLS Server Hello Session ID Heap Buffer Overflow in Palo Alto firewall.&amp;nbsp; In our cutomers Firewall enviroment we not enable the SSL Descryption Feature.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Customers Queries us.. How and Why Palo Alto able detect the Vulnerability threat without the SSL?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can Any one assist us on this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 02 Jul 2018 07:55:15 GMT</pubDate>
    <dc:creator>Nono</dc:creator>
    <dc:date>2018-07-02T07:55:15Z</dc:date>
    <item>
      <title>How Palo Alto Networks Identifies GnuTLS Server Hello Session ID Heap Buffer Over Without Decryption</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/how-palo-alto-networks-identifies-gnutls-server-hello-session-id/m-p/220109#M357</link>
      <description>&lt;P&gt;HI All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We detected&lt;STRONG&gt; Vulnerability:&lt;/STRONG&gt; 36926 ID- GnuTLS Server Hello Session ID Heap Buffer Overflow in Palo Alto firewall.&amp;nbsp; In our cutomers Firewall enviroment we not enable the SSL Descryption Feature.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Customers Queries us.. How and Why Palo Alto able detect the Vulnerability threat without the SSL?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can Any one assist us on this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 02 Jul 2018 07:55:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/how-palo-alto-networks-identifies-gnutls-server-hello-session-id/m-p/220109#M357</guid>
      <dc:creator>Nono</dc:creator>
      <dc:date>2018-07-02T07:55:15Z</dc:date>
    </item>
    <item>
      <title>Re: How Palo Alto Networks Identifies GnuTLS Server Hello Session ID Heap Buffer Over Without Decryp</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/how-palo-alto-networks-identifies-gnutls-server-hello-session-id/m-p/227843#M378</link>
      <description>&lt;P&gt;This is due to the fact that the firewall, or anyone capturing the stream for that matter, can see the start of the server/client session exchange which is still unencrypted.&lt;/P&gt;&lt;P&gt;Looking at the vulnerability "GnuTLS Server Hello Session", the firewall detected something in the server hello. This is the part of an SSL stream where the server and client are still deciding on the way they are going to encrypt the actual session.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Aug 2018 09:29:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/how-palo-alto-networks-identifies-gnutls-server-hello-session-id/m-p/227843#M378</guid>
      <dc:creator>Retired Member</dc:creator>
      <dc:date>2018-08-22T09:29:58Z</dc:date>
    </item>
  </channel>
</rss>

