Skip to content

Use the final SessionSetup UID in SMB1 NTLMSSP authentication (fixes Tree Connect against Samba)#302

Open
Isleynorth wants to merge 1 commit into
rapid7:masterfrom
Isleynorth:bug/301/smb1-session-setup-uid
Open

Use the final SessionSetup UID in SMB1 NTLMSSP authentication (fixes Tree Connect against Samba)#302
Isleynorth wants to merge 1 commit into
rapid7:masterfrom
Isleynorth:bug/301/smb1-session-setup-uid

Conversation

@Isleynorth

Copy link
Copy Markdown

Fixes #301.

SMB1 NTLMSSP smb1_authenticate stored the UID from the challenge response and reused it as the session UID. Servers that assign a new UID in the final STATUS_SUCCESS response, such as Samba, then reject every following request, so the Tree Connect fails with ACCESS_DENIED. Windows keeps the same UID throughout, so this was invisible there.

This stores the UID from the final response instead.

Verification

Signed-off-by: Isleynorth <23055322+Isleynorth@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Todo

Development

Successfully merging this pull request may close these issues.

SMB1 NTLMSSP authentication reuses the challenge UID instead of the final SessionSetup UID (breaks Tree Connect against Samba)

1 participant