<?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: xfinity dns cache poisoning events? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/xfinity-dns-cache-poisoning-events/m-p/3369501#M1041270</link>
    <description>&lt;P&gt;I'll turn the rule back on and try to capture the packets next time it hits.&lt;/P&gt;</description>
    <pubDate>Fri, 20 Apr 2018 04:50:16 GMT</pubDate>
    <dc:creator>Pat Fahey</dc:creator>
    <dc:date>2018-04-20T04:50:16Z</dc:date>
    <item>
      <title>xfinity dns cache poisoning events?</title>
      <link>https://community.cisco.com/t5/network-security/xfinity-dns-cache-poisoning-events/m-p/3363607#M1041266</link>
      <description>&lt;P&gt;Seeing a lot of these events in the log:&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;PROTOCOL-DNS potential dns cache poisoning attempt - mismatched txid (3:21355:5)&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Firepower seems to be finding&amp;nbsp;something&amp;nbsp;about xfinity DNS (75.75.75.75, 75.75.76.76) that it does not like.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Has anyone found a good way to deal with&amp;nbsp;the&amp;nbsp;messages?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thanks for your help.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;----------------------------------------------&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;UPDATE: &amp;nbsp;The message indicates an earlier DNS message format that can be exploited. &amp;nbsp;I solved the problem by disabling the rule.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 15:37:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/xfinity-dns-cache-poisoning-events/m-p/3363607#M1041266</guid>
      <dc:creator>Pat Fahey</dc:creator>
      <dc:date>2020-02-21T15:37:08Z</dc:date>
    </item>
    <item>
      <title>Re: xfinity dns cache poisoning events?</title>
      <link>https://community.cisco.com/t5/network-security/xfinity-dns-cache-poisoning-events/m-p/3368857#M1041268</link>
      <description>&lt;P&gt;It might also indicate that somebody is trying to poison the dns cache.&lt;/P&gt;
&lt;P&gt;DNS uses only a&amp;nbsp;16-bit transaction ID to check the response is valid, although most of the dns servers today will check the TXID is valid a lot of dns responses with false TXID could indicate that somebody is trying to guess the value.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cs.cornell.edu/~shmat/shmat_securecomm10.pdf" target="_blank"&gt;https://www.cs.cornell.edu/~shmat/shmat_securecomm10.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;Bogdan&lt;/P&gt;</description>
      <pubDate>Thu, 19 Apr 2018 10:07:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/xfinity-dns-cache-poisoning-events/m-p/3368857#M1041268</guid>
      <dc:creator>Bogdan Nita</dc:creator>
      <dc:date>2018-04-19T10:07:42Z</dc:date>
    </item>
    <item>
      <title>Re: xfinity dns cache poisoning events?</title>
      <link>https://community.cisco.com/t5/network-security/xfinity-dns-cache-poisoning-events/m-p/3369501#M1041270</link>
      <description>&lt;P&gt;I'll turn the rule back on and try to capture the packets next time it hits.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Apr 2018 04:50:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/xfinity-dns-cache-poisoning-events/m-p/3369501#M1041270</guid>
      <dc:creator>Pat Fahey</dc:creator>
      <dc:date>2018-04-20T04:50:16Z</dc:date>
    </item>
  </channel>
</rss>

