-
Notifications
You must be signed in to change notification settings - Fork 166
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
not really an issue but #8
Comments
you got my question right, the question was towards what if i am on a system and instead of running the exe which is flagged everywhere , to use a manual way to bypass whats needed to extract the hives . however i am receiving a completely different result whats weird is or i dont understand is , shadow copy is protected via UAC , even if i want to use vssadmin list shadows i cant with out the proper permissions . |
You're correct that you can't run the "vssadmin list shadows" without admin access, but you can access those paths in the usual situation. If you look at the Twitter thread associated with this discussion, there are more encompassing answers put forward that will brute force out the Shadow Copy number (really, just put it in a loop and enumerate 1 to x). I cannot replicate the error you're getting however, regardless of whether a path exists, so I'm afraid I can't offer much there. |
is that possible to replicate the vulnrability via powershell / cmd only ?
the exe is being flaged anywhere
The text was updated successfully, but these errors were encountered: