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

"Auth" command after NTLM relay to an HTTP endpoint returns error when getting TGT: KRB_AP_ERR_MODIFIED #102

Closed
Alh4zr3d opened this issue Nov 4, 2022 · 1 comment

Comments

@Alh4zr3d
Copy link

Alh4zr3d commented Nov 4, 2022

When performing a basic NTLM relay attack (with PetitPotam to coerce auth) using the "relay" command, everything goes fine as you see below:

image

The PFX is saved and no error is thrown. However, when you follow this up with a certipy auth as below, a Kerberos error is thrown upon requesting the TGT:

image

However, requesting the TGT and NTLM hash with Rubeus works just as expected:

image

And then I was able to DC Sync with CME using the NTLM hash and/or TGT:

image

The DC involved is a Windows Server 2022 and the CA, on a separate server specifically to facilitate the NTLM relay simulation, is Windows Server 2019. I suspect this may be an issue related to the super up-to-date version of Windows Server that the DC is running on; perhaps Certipy just hasn't been updated to cope with it yet but Rubeus has (it receives more regular updates). Any idea is appreciated, though!

@ly4k
Copy link
Owner

ly4k commented Dec 27, 2022

Hello. If you're still able to test this, Certipy just received a new patch for the authentication part. Can you verify with the latest version?

@ly4k ly4k closed this as completed Jan 18, 2023
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