<?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: OpenSSL SSLv2 Man-in-the-Middle Vulnerability under Top threats in Daily reports in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/openssl-sslv2-man-in-the-middle-vulnerability-under-top-threats/m-p/409210#M92423</link>
    <description>&lt;P&gt;this is a warning that the SSL traffic passing through might be exploited&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;from threatvault.paloaltonetworks.com:&lt;/P&gt;&lt;P&gt;OpenSSL is prone to a man-in-the-middle vulnerability while parsing certain crafted SSL requests. The vulnerability is due to the lack of proper checks on SSL requests, leading to an exploitable man-in-the-middle vulnerability. An attacker could exploit the vulnerability by sending crafted SSL requests. A successful attack could lead to remote code execution with the privileges of the server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;if you go into your threat logs, you should be able to pinpoint where these connections are coming from/going to and take appropriate action (patch server, block connection, add exception)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 26 May 2021 13:20:42 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2021-05-26T13:20:42Z</dc:date>
    <item>
      <title>OpenSSL SSLv2 Man-in-the-Middle Vulnerability under Top threats in Daily reports</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/openssl-sslv2-man-in-the-middle-vulnerability-under-top-threats/m-p/409200#M92421</link>
      <description>&lt;P&gt;I consistently get&amp;nbsp;OpenSSL SSLv2 Man-in-the-Middle Vulnerability under Top Threats in Daily Reports.&lt;/P&gt;&lt;P&gt;What does this mean? am I getting attacked? is it reporting a vulnerability in devices?&amp;nbsp;&lt;/P&gt;&lt;P&gt;At what level should I be concerned with this?&lt;/P&gt;</description>
      <pubDate>Wed, 26 May 2021 13:04:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/openssl-sslv2-man-in-the-middle-vulnerability-under-top-threats/m-p/409200#M92421</guid>
      <dc:creator>ghalbedel</dc:creator>
      <dc:date>2021-05-26T13:04:58Z</dc:date>
    </item>
    <item>
      <title>Re: OpenSSL SSLv2 Man-in-the-Middle Vulnerability under Top threats in Daily reports</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/openssl-sslv2-man-in-the-middle-vulnerability-under-top-threats/m-p/409210#M92423</link>
      <description>&lt;P&gt;this is a warning that the SSL traffic passing through might be exploited&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;from threatvault.paloaltonetworks.com:&lt;/P&gt;&lt;P&gt;OpenSSL is prone to a man-in-the-middle vulnerability while parsing certain crafted SSL requests. The vulnerability is due to the lack of proper checks on SSL requests, leading to an exploitable man-in-the-middle vulnerability. An attacker could exploit the vulnerability by sending crafted SSL requests. A successful attack could lead to remote code execution with the privileges of the server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;if you go into your threat logs, you should be able to pinpoint where these connections are coming from/going to and take appropriate action (patch server, block connection, add exception)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 26 May 2021 13:20:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/openssl-sslv2-man-in-the-middle-vulnerability-under-top-threats/m-p/409210#M92423</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2021-05-26T13:20:42Z</dc:date>
    </item>
  </channel>
</rss>

