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

not really an issue but #8

Open
kolet opened this issue Jul 28, 2021 · 3 comments
Open

not really an issue but #8

kolet opened this issue Jul 28, 2021 · 3 comments

Comments

@kolet
Copy link

kolet commented Jul 28, 2021

is that possible to replicate the vulnrability via powershell / cmd only ?

the exe is being flaged anywhere

@technion
Copy link

Depending on your definition of "replicate":

image

You can copy those SAMs to another machine and:

image

@kolet
Copy link
Author

kolet commented Jul 29, 2021

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
@technion

image

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 .
so what gives ?

@technion
Copy link

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.

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

2 participants