Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DNS ServFail for TXT request #1797

Open
frantz45 opened this issue Oct 18, 2024 · 2 comments
Open

DNS ServFail for TXT request #1797

frantz45 opened this issue Oct 18, 2024 · 2 comments

Comments

@frantz45
Copy link

Hello,

I've an issue with the DNS protocol.
On my lab I've a workstation (192.168.128.2), a bind DNS server (internal IP 192.168.128.10, external IP 185.217.171.10) and the Sliver server (185.217.171.35).
When I execute the DNS implant on the workstation, DNS requests are forwarded to the DNS server which forwards them to Sliver.
At the begining of the connection I can see A requests which seems to work fine, but then the DNS Server rejects the TXT answer.

On the below screenshot you can see a tcpdump capture on Sliver (I think there are multiple identical TXT requests because it fails):
image

On the below screenshot you can see the error on the DNS server:
image

On the below screenshot you can see the DNS server replying ServFail to the workstation:
image

Do you have any idea ?

@frantz45
Copy link
Author

frantz45 commented Oct 18, 2024

It seems related to DNS forwarding. I've succeeded twice to make it work by modifying "forwarders" et "forward only" but now it doesn't.
It's strange, with Cobalt Strike DNS beacon I don't have any issue, but with Sliver I often encounter the "unexpected end of input" error.

I add some debug logs of the Sliver server (it stops at recv: 160 of 264, I never get 264 of 264):
image

@frantz45
Copy link
Author

I did a new test: I configure the workstation to use the Sliver server as the only DNS server (to avoid issues on my intermediate DNS server), and it stops at the same TXT request. Maybe I'm missing something

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant