Wireshark-bugs: [Wireshark-bugs] [Bug 11296] New: Check Ipv4-Header-Total-Length

Date: Mon, 22 Jun 2015 15:01:56 +0000
Bug ID 11296
Summary Check Ipv4-Header-Total-Length
Product Wireshark
Version unspecified
Hardware All
OS All
Status UNCONFIRMED
Severity Enhancement
Priority Low
Component Dissection engine (libwireshark)
Assignee [email protected]
Reporter [email protected]

Created attachment 13681 [details]
7 corrupted testframes, #4+ #6 apply to the enhancement.

Build Information:
Version 1.12.5 (v1.12.5-0-g5819e5b from master-1.12)

Copyright 1998-2015 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 (64-bit) with GTK+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.2.15, with Gcrypt 1.6.2,
without Kerberos, with GeoIP, with PortAudio V19-devel (built May 12 2015),
with
AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 3.2.15, Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz, with 4029MB of physical
memory.


Built using Microsoft Visual C++ 10.0 build 40219
--
PROBLEM:

Wireshark should detect corrupted IPv4 Header field 'Total-Length'
(too-big/too-small).

DETAILS:

A kind of conformancetest sends ethernet frames with always the same IPv4/UDP
payload. For test purpose, the testtool changes single fields of the IP header
only, e.g. the IP-HDR-CRC (which is detected by WS). But if the 'Total Length'
field of the IPv4 Header s varied (too-small/too-big), WS tells nothing -
although WS should be able to detect it with the help of the overall content of
the ethernet frames. 

TEST FRAMES:

I attached a capture with 7 corrupted testframes, where #4 + #6 are the
relevant ones:

    no.4 - IP-Header-Total-Length set to 197 (instead of 192)
    no.6 - IP-Header-Total-Length set to 224 (instead of 192)

OTHER LINKS:

a) Bug ID 10519 seems to cover a similar - but not the same problem.
(https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10519) 

b) This enhancement proposal was issued due to my questions in the WS forum. 
(https://ask.wireshark.org/questions/43432/ws-does-not-check-ipv4-header-total-length)


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