topic Re: Threat log spammed with "Non-RFC Compliant DNS Traffic on Port 53/5353" in General Topics

Threat log spammed with "Non-RFC Compliant DNS Traffic on Port 53/5353"

Maxstr — Thu, 09 Jan 2020 16:31:58 GMT

A couple days ago, the threatvault added threat id 56505, and since then our threat log is getting spammed with the vulnerability type Non-RFC Compliant DNS Traffic on Port 53/5353 (informational). We use dnscrypt, and every single DNS request is now showing up in the threat log. First of all, is this a false positive? And if so, how do I prevent this from inundating my logs?

Re: Threat log spammed with "Non-RFC Compliant DNS Traffic on Port 53/5353"

BPry — Thu, 09 Jan 2020 19:27:58 GMT

@Maxstr,

@Maxstr wrote:
First of all, is this a false positive? And if so, how do I prevent this from inundating my logs?

No, it's not a false positive; it also isn't unexpected if you are utilizing dnscrypt. DNSCrypt is not RFC compliant, hence you are hitting a signature that makes perfect sense. If you don't want it to keep showing up in your logs, you'll need to make an exception for 56505 on your Vulnerability profile and set it to allow.

Re: Threat log spammed with "Non-RFC Compliant DNS Traffic on Port 53/5353"

felcor — Mon, 18 Oct 2021 18:31:04 GMT

Helo All,

In my case I dont have DNSDecry and I see threat id 56112 .

It is possible I consider a false positive ?

Re: Threat log spammed with "Non-RFC Compliant DNS Traffic on Port 53/5353"

MP18 — Tue, 19 Oct 2021 01:38:39 GMT

@felcor

It is not false positive. It is information message only.

https://threatvault.paloaltonetworks.com/?query=56505

Regards

Re: Threat log spammed with "Non-RFC Compliant DNS Traffic on Port 53/5353"

mss-ops — Fri, 21 Jan 2022 05:18:48 GMT

Name: Non-RFC Compliant DNS Traffic on Port 53/5353

56505

What is the solution for this, and what RFC standard it is not cpmpliant?