| Bug ID | 
          9523
           | 
        
        
          | Summary | 
          ISO 10747 (IDRP) incorrect handling of data in IDRP ERROR PDU's
           | 
        
        
          | Classification | 
          Unclassified
           | 
        
        
          | Product | 
          Wireshark
           | 
        
        
          | Version | 
          SVN
           | 
        
        
          | Hardware | 
          All
           | 
        
        
          | OS | 
          All
           | 
        
        
          | Status | 
          UNCONFIRMED
           | 
        
        
          | Severity | 
          Trivial
           | 
        
        
          | Priority | 
          Low
           | 
        
        
          | Component | 
          Dissection engine (libwireshark)
           | 
        
        
          | Assignee | 
          [email protected]
           | 
        
        
          | Reporter | 
          [email protected]
           | 
        
      
        
        Created attachment 12255 [details]
Fix for incorrect handling of data in IDRP ERROR PDU's
Build Information:
TShark 1.11.3 (SVN Rev 53818 from /trunk)
Copyright 1998-2013 Gerald Combs <[email protected]> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (32-bit) with GLib 2.32.4, with libpcap, with libz 1.2.7, without
POSIX
capabilities, without libnl, without SMI, without c-ares, without ADNS, without
Lua, without Python, with GnuTLS 2.12.20, with Gcrypt 1.5.0, without Kerberos,
with GeoIP.
Running on Linux 3.2.0-4-486, with locale en_US.UTF-8, with libpcap version
1.3.0, with libz 1.2.7.
Built using gcc 4.7.2.
--
ISO 10747 (IDRP) ERROR PDU's are not correctly displayed if no additional data
is present; this happens because 'proto_tree_add_item' is incorrectly called
with a length parameter with the value of '0'.
         
      
      
      You are receiving this mail because:
      
      
          - You are watching all bug changes.