Actions
Bug #5258
closedsmb/ntlmssp: parser incorrectly assumes fixed field order
Affected Versions:
Effort:
Difficulty:
Label:
Description
"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.
Actions