ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 12851] Buildbot crash output: fuzz-2016-09-09-25074.pcap

Date: Thu, 22 Sep 2016 12:34:48 +0000

Comment # 5 on bug 12851 from
(In reply to Birol Capa from comment #4)
> As far as I understand from your answer, this file is used to find find bugs
> at the dissector. That's why it has so many malformed frames.

Correct.

> Cyclic message data dissection is based on Connect Request frames.
> Then there should be a change as following:
> 
> If connect request frames are malformed then don't dissect cyclic frame data.
> 
> If connect request messages are not malformed then dissect cyclic frame data.
> 
> Do you agree with this strategy?

Not necessarily.  While I didn't look at the trace yet, the goal of Wireshark
is to dissect "as much as possible".  Based on the recent additions to the
Profinet dissector, I thought the issue would be with all of the "device
information" being stored and retrieved.  And the handling of that, may not
correctly handle "bad data"/malformed packet.


You are receiving this mail because:
  • You are watching all bug changes.