| Bug ID |
13097
|
| Summary |
Buildbot crash output: fuzz-2016-11-04-25886.pcap
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
https://www.wireshark.org/download/automated/captures/fuzz-2016-11-04-25886.pcap
|
| OS |
Ubuntu
|
| Status |
CONFIRMED
|
| Severity |
Major
|
| Priority |
High
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Problems have been found with the following capture file:
https://www.wireshark.org/download/automated/captures/fuzz-2016-11-04-25886.pcap
stderr:
Input file:
/home/wireshark/menagerie/menagerie/3764-DTNPing_LongIncarnations.wireshark
Build host information:
Linux wsbb04 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial
Buildbot information:
BUILDBOT_REPOSITORY=ssh://[email protected]:29418/wireshark
BUILDBOT_WORKERNAME=fuzz-test
BUILDBOT_BUILDNUMBER=219
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.0/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=a6d7c42f965ca54265e03a288203f0c2fc9f7f2e
Return value: 152
Dissector bug: 0
Valgrind error count: 0
Git commit
commit a6d7c42f965ca54265e03a288203f0c2fc9f7f2e
Author: Guy Harris <[email protected]>
Date: Wed Nov 2 18:57:12 2016 -0700
RTS_FLAG_NONE is a flags field value, but it's not a flag bit.
It's the *absence* of flag bits, so you can't test whether it's set;
don't have a field for it. This gets rid of a dissector assertion.
Add some more URLs for information about DCE RPC and MS-RPC.
Change-Id: I53e8f11692c66e16ae2ec7fd4ba8eb90b0673da4
Reviewed-on: https://code.wireshark.org/review/18648
Reviewed-by: Guy Harris <[email protected]>
(cherry picked from commit eb56b7172d33605cbb969afd91beb302f89013ed)
Reviewed-on: https://code.wireshark.org/review/18650
Command and args: ./tools/valgrind-wireshark.sh
==11844== Memcheck, a memory error detector
==11844== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==11844== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==11844== Command:
/home/wireshark/builders/wireshark-2.0-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.0/fuzz-2016-11-04-25886.pcap
==11844==
==11844==
==11844== Process terminating with default action of signal 24 (SIGXCPU):
dumping core
==11844== at 0x6ACCADC: evaluate_sdnv (packet-dtn.c:1651)
==11844== by 0x6ACEDF6: display_metadata_block (packet-dtn.c:1508)
==11844== by 0x6ACEDF6: dissect_bundle (packet-dtn.c:2077)
==11844== by 0x685E30E: call_dissector_through_handle (packet.c:618)
==11844== by 0x685EC94: call_dissector_work (packet.c:706)
==11844== by 0x6860E21: call_dissector_with_data (packet.c:2563)
==11844== by 0x6ACD601: dissect_tcpcl_pdu (packet-dtn.c:1887)
==11844== by 0x6FAB261: tcp_dissect_pdus (packet-tcp.c:2750)
==11844== by 0x6ACC9B1: dissect_tcpcl (packet-dtn.c:2013)
==11844== by 0x685E30E: call_dissector_through_handle (packet.c:618)
==11844== by 0x685EC94: call_dissector_work (packet.c:706)
==11844== by 0x685F4D8: dissector_try_uint_new (packet.c:1163)
==11844== by 0x6FAB5AC: decode_tcp_ports (packet-tcp.c:4610)
==11844==
==11844== HEAP SUMMARY:
==11844== in use at exit: 18,329,282 bytes in 190,559 blocks
==11844== total heap usage: 243,414 allocs, 52,855 frees, 31,466,010 bytes
allocated
==11844==
==11844== LEAK SUMMARY:
==11844== definitely lost: 251 bytes in 17 blocks
==11844== indirectly lost: 0 bytes in 0 blocks
==11844== possibly lost: 0 bytes in 0 blocks
==11844== still reachable: 18,329,031 bytes in 190,542 blocks
==11844== suppressed: 0 bytes in 0 blocks
==11844== Rerun with --leak-check=full to see details of leaked memory
==11844==
==11844== For counts of detected and suppressed errors, rerun with: -v
==11844== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1 from 1)
./tools/valgrind-wireshark.sh: line 113: 11844 CPU time limit exceeded (core
dumped) $LIBTOOL valgrind --suppressions=`dirname $0`/vg-suppressions
--tool=$TOOL $CALLGRIND_OUT_FILE $VERBOSE $LEAK_CHECK $REACHABLE $TRACK_ORIGINS
$COMMAND $COMMAND_ARGS $PCAP $COMMAND_ARGS2 > /dev/null
[ no debug trace ]
You are receiving this mail because:
- You are watching all bug changes.