<?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: We have enabled ssl inbound decryption and able to exploit the vulnerab in Advanced Threat Prevention Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/we-have-enabled-ssl-inbound-decryption-and-able-to-exploit-the/m-p/326557#M808</link>
    <description>&lt;P&gt;Sounds like a false negative, but the forum is not the right place to troubleshoot this. Please open a Support case. You will be asked to provide the exploit PoC, a packet capture of the attack (capture it from the client side) and supporting evidence that SSL decryption is working properly (detailed traffic log view showing the decrypted application normally detected and readable by the firewall).&lt;/P&gt;</description>
    <pubDate>Wed, 06 May 2020 23:26:21 GMT</pubDate>
    <dc:creator>mivaldi</dc:creator>
    <dc:date>2020-05-06T23:26:21Z</dc:date>
    <item>
      <title>We have enabled ssl inbound decryption and able to exploit the vulnerabilty</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/we-have-enabled-ssl-inbound-decryption-and-able-to-exploit-the/m-p/326341#M805</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have ssl inbound &amp;nbsp;decryption configured &amp;nbsp;and from outside we are able to exploit the vulnerabilty.&lt;/P&gt;&lt;P&gt;Need to know why PA allows the connection for that signature.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Vul &amp;nbsp;threat id is 57230&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Name Telerik Web UI&lt;/P&gt;</description>
      <pubDate>Wed, 06 May 2020 12:53:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/we-have-enabled-ssl-inbound-decryption-and-able-to-exploit-the/m-p/326341#M805</guid>
      <dc:creator>MP18</dc:creator>
      <dc:date>2020-05-06T12:53:38Z</dc:date>
    </item>
    <item>
      <title>Re: We have enabled ssl inbound decryption and able to exploit the vulnerab</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/we-have-enabled-ssl-inbound-decryption-and-able-to-exploit-the/m-p/326557#M808</link>
      <description>&lt;P&gt;Sounds like a false negative, but the forum is not the right place to troubleshoot this. Please open a Support case. You will be asked to provide the exploit PoC, a packet capture of the attack (capture it from the client side) and supporting evidence that SSL decryption is working properly (detailed traffic log view showing the decrypted application normally detected and readable by the firewall).&lt;/P&gt;</description>
      <pubDate>Wed, 06 May 2020 23:26:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/we-have-enabled-ssl-inbound-decryption-and-able-to-exploit-the/m-p/326557#M808</guid>
      <dc:creator>mivaldi</dc:creator>
      <dc:date>2020-05-06T23:26:21Z</dc:date>
    </item>
    <item>
      <title>Re: We have enabled ssl inbound decryption and able to exploit the vulnerab</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/we-have-enabled-ssl-inbound-decryption-and-able-to-exploit-the/m-p/327088#M811</link>
      <description>&lt;P&gt;I agree we have opened the case with PA for 10 days as per them decryption is working as expected.&lt;/P&gt;&lt;P&gt;They are looking into this vulnerability as we can exploit the signature.&lt;/P&gt;</description>
      <pubDate>Fri, 08 May 2020 19:19:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/we-have-enabled-ssl-inbound-decryption-and-able-to-exploit-the/m-p/327088#M811</guid>
      <dc:creator>MP18</dc:creator>
      <dc:date>2020-05-08T19:19:56Z</dc:date>
    </item>
    <item>
      <title>Re: We have enabled ssl inbound decryption and able to exploit the vulnerab</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/we-have-enabled-ssl-inbound-decryption-and-able-to-exploit-the/m-p/333544#M855</link>
      <description>&lt;P&gt;PA is still searching on this.&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jun 2020 21:41:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/we-have-enabled-ssl-inbound-decryption-and-able-to-exploit-the/m-p/333544#M855</guid>
      <dc:creator>MP18</dc:creator>
      <dc:date>2020-06-15T21:41:05Z</dc:date>
    </item>
    <item>
      <title>Re: We have enabled ssl inbound decryption and able to exploit the vulnerab</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/we-have-enabled-ssl-inbound-decryption-and-able-to-exploit-the/m-p/334495#M863</link>
      <description>&lt;P&gt;Seems Palo Alto did the content upgrade on their end recently and now we see that signature is blocking the traffic.&lt;/P&gt;</description>
      <pubDate>Sun, 21 Jun 2020 16:04:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/we-have-enabled-ssl-inbound-decryption-and-able-to-exploit-the/m-p/334495#M863</guid>
      <dc:creator>MP18</dc:creator>
      <dc:date>2020-06-21T16:04:15Z</dc:date>
    </item>
  </channel>
</rss>

