This repository has been archived by the owner on Apr 26, 2021. It is now read-only.
Elevate Permissions to avoid Ransomeware Crashes #3136
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.
Thanks for contributing! But first: did you read our community guidelines?
https://cuckoo.sh/docs/introduction/community.html
What I have added/changed is:
Auxiliary module that elevates permissions for certain directories and all files/sub-directories such that only SYSTEM has write access.
The goal of my change is:
When dealing with certain ransomware samples, such as
d9c3e675971499e4a2c0677b5ae96cd5582900e7cbfc16a00555ec90335aaebf
, they arbitrarily encrypt all files in all directories located atC:\\
. This is where the Python interpreter and the injected directory used for analysis are located, and thus they get encrypted and the connection required for analysis breaks. If we elevate the permissions required to write to these directories to exclude Administrators and lower, then this connection prevails and we are able to get the full analysis of this sample.What I have tested about my change is:
General functionality via manual testing.