Project

General

Profile

Actions
Copy link

Bug #5258

closed
VJ PA

smb/ntlmssp: parser incorrectly assumes fixed field order

Bug #5258: smb/ntlmssp: parser incorrectly assumes fixed field order

Added by Victor Julien almost 4 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Philippe Antoine
Target version:
7.0.0-rc1
Affected Versions:
Effort:
Difficulty:
Label:

Description

https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-nlmp/033d32cc-88f9-4483-9bf2-b273055038ce

"Payload (variable): A byte array that contains the data referred to by the LmChallengeResponseBufferOffset, NtChallengeResponseBufferOffset, DomainNameBufferOffset, UserNameBufferOffset, WorkstationBufferOffset, and EncryptedRandomSessionKeyBufferOffset message fields. Payload data can be present in any order within the Payload field, with variable-length padding before or after the data. The data that can be present in the Payload field of this message, in no particular order, are:"

Currently we assume a strict ordering.

Subtasks 1 (0 open — 1 closed)

Bug #5810: smb/ntlmssp: parser incorrectly assumes fixed field order (6.0.x backport)ClosedPhilippe AntoineActions
Actions
Copy link

Also available in: PDF Atom