04-10-2018 10:15 AM - edited 02-21-2020 07:37 AM
Seeing a lot of these events in the log:
PROTOCOL-DNS potential dns cache poisoning attempt - mismatched txid (3:21355:5)
Firepower seems to be finding something about xfinity DNS (75.75.75.75, 75.75.76.76) that it does not like.
Has anyone found a good way to deal with the messages?
Thanks for your help.
----------------------------------------------
UPDATE: The message indicates an earlier DNS message format that can be exploited. I solved the problem by disabling the rule.
04-19-2018 03:07 AM
It might also indicate that somebody is trying to poison the dns cache.
DNS uses only a 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.
https://www.cs.cornell.edu/~shmat/shmat_securecomm10.pdf
HTH
Bogdan
04-19-2018 09:50 PM
I'll turn the rule back on and try to capture the packets next time it hits.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide