DNS Exfiltration Method Fixes #89
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Python 3.10+ fixes - Upstream case insensitive DNS server fixes - PowerShell client updated for hexadecimal resolved DNS method
- Python 3.12+ fixes
- Fixed PowerShell DNS server retrieval process
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We were planning to use Egress Assess for a DNS exfiltration exercise for a client of Maveris' when we were quickly met with Python exceptions. The first interpreter we used was Python 3.10 and it was discovered the current Python code is broken out of the box with this version. From my understanding, core libraries in updated Python versions changed some APIs and were expecting data of different types. After this, we discovered the DNS resolved method used base64 for the subdomains. This is an issue if the environment uses upstream DNS servers which can scramble the casing of the subdomain and randomize it and all decoded base64 will be inaccurate. Hence, it was replaced with hexadecimal. It was then run with a different Python interpreter (3.12) where further issues were discovered and ultimately fixed due to library changes.