[Wireshark-bugs] [Bug 13232] Buildbot crash output: fuzz-2016-12-09-9689.pcap

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13232

--- Comment #28 from Michael Mann  ---
*** Bug 13667 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13667] Buildbot crash output: fuzz-2017-04-26-29121.pcap

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13667

Michael Mann  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED

--- Comment #1 from Michael Mann  ---


*** This bug has been marked as a duplicate of bug 13232 ***

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13637] [oss-fuzz] UBSAN: null pointer passed as argument 1, which is declared to never be null in wmem_map.c:419:57

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13637

Michael Mann  changed:

   What|Removed |Added

 CC||darkjames...@darkjames.pl

--- Comment #6 from Michael Mann  ---
*** Bug 13600 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13599] libfuzzer: BZR dissector loop (get_bzr_pdu_len)

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13599

Peter Wu  changed:

   What|Removed |Added

  Comment #0 is|1   |0
private||
  Group|private, core   |

--- Comment #10 from Peter Wu  ---
(Marking bug as public)

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13690] New: SMB protocol parser does not parse SMB_COM_TRANSACTION2_SECONDARY (0x33) command correctly

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13690

Bug ID: 13690
   Summary: SMB protocol parser does not parse
SMB_COM_TRANSACTION2_SECONDARY (0x33) command
correctly
   Product: Wireshark
   Version: 2.2.6
  Hardware: x86-64
OS: All
Status: UNCONFIRMED
  Severity: Major
  Priority: Low
 Component: Dissection engine (libwireshark)
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: alexwe...@gmail.com
  Target Milestone: ---

Build Information:
Version 2.2.6 (v2.2.6-0-g32dac6a)
--
Hi, when you parsing SMB protocol requests you parse
SMB_COM_TRANSACTION2 (0x32) command and SMB_COM_TRANSACTION2_SECONDARY (0x33)
command
as commands that have the equal request parameters structure. But this is
mistake.

SMB_COM_TRANSACTION2_SECONDARY command have it's own parameters structure:

SMB_Parameters { 
UCHAR WordCount;
Words 
{ 
USHORT TotalParameterCount;
USHORT TotalDataCount;
USHORT ParameterCount;
USHORT ParameterOffset;
USHORT ParameterDisplacement;
USHORT DataCount;
USHORT DataOffset;
USHORT DataDisplacement;
USHORT FID;
} 
} 

SMB_Data { 
USHORT ByteCount;
Bytes { UCHAR Pad1[];
UCHAR Trans2_Parameters[ParameterCount];
UCHAR Pad2[];
UCHAR Trans2_Data[DataCount];
} 
}

Detailed here:
https://msdn.microsoft.com/en-us/library/ee442192.aspx
https://msdn.microsoft.com/en-us/library/ee442105.aspx

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe