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.
Updated by Victor Julien almost 2 years ago
- Status changed from New to Assigned
- Assignee changed from OISF Dev to Philippe Antoine
- Target version changed from TBD to 7.0.0-rc1
Updated by Victor Julien almost 2 years ago
- Priority changed from Normal to High
Updated by Philippe Antoine almost 2 years ago
- Status changed from Assigned to In Review
Updated by Victor Julien almost 2 years ago
- Status changed from In Review to Closed
- Priority changed from High to Normal
- Label Needs backport to 6.0 added
Updated by Shivani Bhardwaj almost 2 years ago
- Status changed from Closed to Resolved
Updated by Shivani Bhardwaj almost 2 years ago
- Label deleted (
Needs backport to 6.0)
Updated by Philippe Antoine almost 2 years ago
- Status changed from Resolved to Closed
Actions