Bug ID |
8362
|
Summary |
Checksum calculation is wrong for some IPv6 packets
|
Classification |
Unclassified
|
Product |
Wireshark
|
Version |
1.8.5
|
Hardware |
x86-64
|
OS |
All
|
Status |
UNCONFIRMED
|
Severity |
Major
|
Priority |
Medium
|
Component |
Dissection engine (libwireshark)
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Build Information:
wireshark 1.8.5 (SVN Rev Unknown from unknown)
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 (64-bit) with GTK+ 2.24.10, with Cairo 1.12.2, with Pango 1.30.1, with
GLib 2.32.4, with libpcap, without libz, with POSIX capabilities (Linux), with
SMI 0.4.8, with c-ares 1.7.5, with Lua 5.1, without Python, without GnuTLS,
with
Gcrypt 1.5.0, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built
Apr
2 2012 11:03:56), with AirPcap.
Running on Linux 3.4.11-2.16-desktop, with locale POSIX, with libpcap version
1.2.1, Gcrypt 1.5.0, without AirPcap.
Built using gcc 4.7.1 20120723 [gcc-4_7-branch revision 189773].
--
When decoding some crafted IPv6 packets carrying more than one Fragment EH,
Wireshark will report a bad checksum on the payload - while in fact the
checksum is correct.
Attaching pcap showing the issue and script for scapy to recreate. Issue is
shown w/ ICMPv6 - all packets are exactly the same (with the addition of Frag
EHs), and Wireshark is reporting an error on packet #13 - "should be 0xa3b2"
You are receiving this mail because:
- You are watching all bug changes.