Replies: 2 comments 2 replies
-
Good idea to check which GPOs exist! Might be a bit hard to find which GPOs apply to your target, but still worth a try. I have also done something similar in wsuks which parses GPOs to find the WSUS registry setting. If you craft something similar feel free to open up a PR |
Beta Was this translation helpful? Give feedback.
2 replies
-
also pingcastle applies a similar method. https://github.com/netwrix/pingcastle/blob/master/Healthcheck/Rules/HeatlcheckRuleStaledOldNtlm.cs |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Was doing an engagement recently and was playing around with a new tool called GPOHound, which analyzes GPOs after you download them from the SYSVOL folder of a DC. One of the things it shows is the LmCompatibilityLevel from the Default Domain Controller Policy.
After reading #260 and #173, and seeing the new functionality added in #320 and #493, this might be an interesting feature to add, which would allow a low-privileged user to enumerate this setting without admin privileges and without attempting any coercion.
I'm not sure if the value in the GPO is the actual value for all DCs, but it was for this engagement. Just wanted to bring it up.
Edit: Actually just saw that GPOHunter does this (albeit, misses cases which are vulnerable due to LmCompatiblityLevel = 2):
Beta Was this translation helpful? Give feedback.
All reactions