| Bug ID |
10552
|
| Summary |
Buildbot crash output: fuzz-2014-10-09-26445.pcap
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
https://www.wireshark.org/download/automated/captures/fuzz-2014-10-09-26445.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-2014-10-09-26445.pcap
stderr:
Input file: /home/wireshark/menagerie/menagerie/oldenb
Build host information:
Linux wsbb04 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 14.04.1 LTS
Release: 14.04
Codename: trusty
Buildbot information:
BUILDBOT_REPOSITORY=
BUILDBOT_BUILDNUMBER=201
BUILDBOT_URL=http://buildbot.wireshark.org/master-1.12/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_SLAVENAME=fuzz-test
BUILDBOT_GOT_REVISION=eaccf31847a36d6025987d19700843d8eded339b
Return value: 134
Dissector bug: 0
Valgrind error count: 0
Git commit
commit eaccf31847a36d6025987d19700843d8eded339b
Author: Anish Bhatt <[email protected]>
Date: Tue Oct 7 14:48:13 2014 -0400
[iSCSI] Fix incorrect heuristic.
The only valid check for Expected Data Transfer Length is :
R and W MUST NOT both be 0 when the Expected Data Transfer Length
and/or
Bidirectional Read Expected Data Transfer Length are not 0
Backported with manual intervention from
I5503a5ad524c4e237b143696fc8eda895bcb9172
with change to reflect v1.12 version of packet-isci.c code.
Ping-Bug: 10469
Change-Id: I4b3ed968a092ff3a6704f94f4517d45793a599cf
Reviewed-on: https://code.wireshark.org/review/4530
Reviewed-by: Michael Mann <[email protected]>
Command and args:
/home/wireshark/builders/wireshark-1.12-fuzz/fuzztest/install/bin/tshark -nVxr
*** stack smashing detected ***:
/home/wireshark/builders/wireshark-1.12-fuzz/fuzztest/install/bin/tshark
terminated
[ no debug trace ]
You are receiving this mail because:
- You are watching all bug changes.