-
-
Notifications
You must be signed in to change notification settings - Fork 391
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
function VulnAD-Kerberoasting Unsuccessful #14
Comments
Hello, @mbb5546 , give a go this command (PowerView must be loaded prior to this): It worked for me, I found all 3 of them: However, the issue I encountered was related to the cryptography. All the tickets I tried to request were AES-encrypted, I couldn't request RC4 tickets at all. [*] Target SPN : http_svc/httpserver.cs.org I've already tried to use "usetgtdeleg" or "tgtdeleg" instead of "rc4opsec"; however, nothing worked :( At some point I enabled all the encryption algos (RC4, AES128, AES256 etc), and yet - all the tickets were AES encrypted. I'm still eager to find out if there's the "intended way" to Kerberoast Windows Server 2019. Dear @WazeHell , please help :) |
PS: I found one more "vuln AD script" (BadBlood), but they create Users instead of Managed Service Accounts:
|
Hi, I have the same problem as mbb5546, but the command "get-adobject | Where-Object {$.serviceprincipalname -ne $null -and $.cn -ne "krbtgt"}" doesn't resolve my problem, any idea for this? |
Uploaded and Ran the script on my Windows Server 2019 Domain controller. I ran the script once I already had my domain created. After deleting the banner function the script ran fine but when I went to perform a Kerberoasting attack there were no accounts configured with SPN's.
I know I can do this manually which I plan to do, just wanted to open an issue for visibility incase anyone else noticed this
The text was updated successfully, but these errors were encountered: