<?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: DNS MX record null prefix in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DNS-MX-record-null-prefix/m-p/32821#M58100</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is related to CVE-2010-0024.&lt;/P&gt;&lt;P&gt;Presumably there is something related to the MX response being received from 4.2.2.2 that can cause a problem in some older, unpatched versions of Windows Server, which don't parse MX records properly.&lt;/P&gt;&lt;P&gt;By default, this signature is not enabled except on the Strict profile in Detect mode only.&lt;/P&gt;&lt;P&gt;If you think this is in error, you should open a TAC case OR add an exception in your Threat Prevention profile.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 14 Feb 2019 04:21:46 GMT</pubDate>
    <dc:creator>PhoneBoy</dc:creator>
    <dc:date>2019-02-14T04:21:46Z</dc:date>
    <item>
      <title>DNS MX record null prefix</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DNS-MX-record-null-prefix/m-p/32819#M58098</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is a signature triggered on ips. So i just wanted to know when it will trigger.&lt;/P&gt;&lt;P&gt;Kindly help me with this&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Feb 2019 03:17:53 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DNS-MX-record-null-prefix/m-p/32819#M58098</guid>
      <dc:creator>Sameer_Ahammed</dc:creator>
      <dc:date>2019-02-13T03:17:53Z</dc:date>
    </item>
    <item>
      <title>Re: DNS MX record null prefix</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DNS-MX-record-null-prefix/m-p/32820#M58099</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The traffic is actually from mail gateway to 4.2.2.2(dns)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Feb 2019 03:19:25 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DNS-MX-record-null-prefix/m-p/32820#M58099</guid>
      <dc:creator>Sameer_Ahammed</dc:creator>
      <dc:date>2019-02-13T03:19:25Z</dc:date>
    </item>
    <item>
      <title>Re: DNS MX record null prefix</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DNS-MX-record-null-prefix/m-p/32821#M58100</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is related to CVE-2010-0024.&lt;/P&gt;&lt;P&gt;Presumably there is something related to the MX response being received from 4.2.2.2 that can cause a problem in some older, unpatched versions of Windows Server, which don't parse MX records properly.&lt;/P&gt;&lt;P&gt;By default, this signature is not enabled except on the Strict profile in Detect mode only.&lt;/P&gt;&lt;P&gt;If you think this is in error, you should open a TAC case OR add an exception in your Threat Prevention profile.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Feb 2019 04:21:46 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/DNS-MX-record-null-prefix/m-p/32821#M58100</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2019-02-14T04:21:46Z</dc:date>
    </item>
  </channel>
</rss>

