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

Relay fails when client requires SMB signing #227

Open
spextat0r opened this issue Oct 1, 2024 · 1 comment
Open

Relay fails when client requires SMB signing #227

spextat0r opened this issue Oct 1, 2024 · 1 comment

Comments

@spextat0r
Copy link

So as the title alludes Certipy v4.8.2 seems to fail to relay to both RPC and HTTP when the client has Require SMB Signing turned on. ntlmrelayx does not seem to have this issue and inspecting the SMB negotiation protocol with Wireshark between the two tools I cannot see an difference between the two other than Certipy sending a STATUS_MORE_PROCESSING_REQUIRED flag after the NTLMSSP_NEGOTIATE packet.

image
image

Googling the SMB error I get a Microsoft Page titled "System error 2148073478, extended error, or Invalid Signature error message on SMB connections in Windows Server 2012 or Windows 8" so it seems that the issue is indeed tied to SMB Signing

Setting client signing to be if server agrees this is the new output

image
image

Looking at the Wireshark capture this is all that occurs when signing is required

image

Here is the same required signing settings but with ntlmrelayx

image

@l33tluigi
Copy link

I have also encountered this issue a few times

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