- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
10-17-2018 10:18 AM
need to understand deeply reset both action by PA for dns query in threat logs
I know PA send the tcp fin to both ends.
But client who is doing dns query if it does not get reply what does it shows there ?
does the client again makes query?
or does PA allow some traffic and drops some?
how can i fgure this out?
10-17-2018 11:07 AM
The client makes the request a set number of times (depends on platform) and since it's not recieving a request will eventually time-out. The client can attempt to make the same query many times attempting to get a response, but it depends on the client.
Generally speaking you won't really set the action to reset-both for DNS signatures; you would drop them or sinkhole the request.
10-18-2018 08:12 AM - edited 10-18-2018 08:13 AM
Hey @MP18
When using the reset-both action the behaviour is different depending on whether the protocol is UDP or TCP
For TCP:
A TCP-RST (reset) packet is sent to both the client and the server.
For UDP:
The firewall simply drops or discards the session.
Since DNS is UDP, in this scenario the DNS request will be dropped. From the client perspective, it would look something like a timeout or no response. It is then application dependant on whether the DNS query is attempted again.
Thanks,
Luke.
10-18-2018 10:03 AM
That's what I was running into as well.
@MP18, You might want to reach out to support and see if there is a way to re-base the signature database. Off hand I can't think of how you would go about doing so. You could also safetly exclude this signature from your threat profiles, as I pretty positive the signature should have been removed from your system.
10-18-2018 10:12 AM
You'll sometimes see the threats get pulled back for various reasons. Whether the threat campaign is no longer active, or if the signature was too broad and caught traffic that it wasn't designed/supposed to.
10-17-2018 11:07 AM
The client makes the request a set number of times (depends on platform) and since it's not recieving a request will eventually time-out. The client can attempt to make the same query many times attempting to get a response, but it depends on the client.
Generally speaking you won't really set the action to reset-both for DNS signatures; you would drop them or sinkhole the request.
10-17-2018 12:12 PM
it is for IDF 54122
Exim DKIM DNS Decoding Buffer Overflow Vulnerability
10-17-2018 12:25 PM
Can you check your Applications and Threats version for me real quick; I'm pretty sure that 54122 was pulled a while back.
10-17-2018 03:21 PM
i am running 8080-5081
10-18-2018 08:12 AM - edited 10-18-2018 08:13 AM
Hey @MP18
When using the reset-both action the behaviour is different depending on whether the protocol is UDP or TCP
For TCP:
A TCP-RST (reset) packet is sent to both the client and the server.
For UDP:
The firewall simply drops or discards the session.
Since DNS is UDP, in this scenario the DNS request will be dropped. From the client perspective, it would look something like a timeout or no response. It is then application dependant on whether the DNS query is attempted again.
Thanks,
Luke.
10-18-2018 09:46 AM
Specific to your Threat ID you have listed, @LukeBullimore could you look at one of your firewalls and see if you have the specified threat ID?
The ID that you've specified isn't present on any of my appliances, or a fresh VM install. I'm kind of wondering if you someone didn't get a signature "stuck" on your firewall that has since been pulled.
10-18-2018 09:55 AM
Hey @BPry
I couldn't find that TID on any of the firewalls I checked. I'm looking at the Threat Vault for that TID and also "DNS Decoding Buffer Overflow Vulnerability" but I'm finding nothing - so I definitely think you're right in saying that this has been pulled.
I get emailed every time there is a new content update, and I'm not able to find anything by searching through my emails either.
10-18-2018 10:03 AM
That's what I was running into as well.
@MP18, You might want to reach out to support and see if there is a way to re-base the signature database. Off hand I can't think of how you would go about doing so. You could also safetly exclude this signature from your threat profiles, as I pretty positive the signature should have been removed from your system.
10-18-2018 10:11 AM
yes you are right unable to find this signature any more.
Seems it is pulled back.
Good to know that updates can also remove the signature if not needed any more.
10-18-2018 10:12 AM
You'll sometimes see the threats get pulled back for various reasons. Whether the threat campaign is no longer active, or if the signature was too broad and caught traffic that it wasn't designed/supposed to.
10-18-2018 10:14 AM
learned something new.
Many thanks for answering the questions.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!