Wireshark-bugs: [Wireshark-bugs] [Bug 12681] New: Buildbot crash output: fuzz-2016-07-28-14141.p

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 28 Jul 2016 04:30:03 +0000
Bug ID 12681
Summary Buildbot crash output: fuzz-2016-07-28-14141.pcap
Product Wireshark
Version unspecified
Hardware x86-64
URL https://www.wireshark.org/download/automated/captures/fuzz-2016-07-28-14141.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-07-28-14141.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/0000.cap

Build host information:
Linux wsbb04 3.13.0-92-generic #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID:    Ubuntu
Description:    Ubuntu 14.04.4 LTS
Release:    14.04
Codename:    trusty

Buildbot information:
BUILDBOT_REPOSITORY=ssh://[email protected]:29418/wireshark
BUILDBOT_BUILDNUMBER=12
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.2/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_SLAVENAME=fuzz-test
BUILDBOT_GOT_REVISION=6eebb5aa8b8590233d625a9a8e2f0012579c79fe

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit 6eebb5aa8b8590233d625a9a8e2f0012579c79fe
Author: Peter Wu <[email protected]>
Date:   Tue Jul 26 00:14:40 2016 +0200

    ssl-utils: ensure that the cipher suite matches decoder

    When the cipher suite for the current decryption session is changed via
    a Server Hello, it should not change the cipher suite field of the
    decoder. Otherwise there is a mismatch between the cipher suite and the
    capabilities of the decoder.

    Fix this issue by making the decoder hold a pointer to the (constant)
    SslCipherSuite structure rather than making a copy (and have the decoder
    point to that data).

    I also considered resetting the decoder once the cipher suite changes in
    the Server Hello, but that breaks renegotiation.

    Bug: 12665
    Change-Id: Ieff38a535cd111d95933ec383378643b6fbab7bf
    Reviewed-on: https://code.wireshark.org/review/16674
    Reviewed-by: Pascal Quantin <[email protected]>
    Petri-Dish: Pascal Quantin <[email protected]>
    Tested-by: Petri Dish Buildbot <[email protected]>
    Reviewed-by: Peter Wu <[email protected]>
    (cherry picked from commit ae0f130582c36978908a965aed32e446ba8d40db)
    Reviewed-on: https://code.wireshark.org/review/16716


==14196== Memcheck, a memory error detector
==14196== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==14196== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==14196== Command:
/home/wireshark/builders/wireshark-2.2-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.2/fuzz-2016-07-28-14141.pcap
==14196== 
==14196== 
==14196== HEAP SUMMARY:
==14196==     in use at exit: 1,511,676 bytes in 39,714 blocks
==14196==   total heap usage: 264,741 allocs, 225,027 frees, 30,438,535 bytes
allocated
==14196== 
==14196== LEAK SUMMARY:
==14196==    definitely lost: 332,918 bytes in 148 blocks
==14196==    indirectly lost: 725,246 bytes in 29,927 blocks
==14196==      possibly lost: 0 bytes in 0 blocks
==14196==    still reachable: 453,512 bytes in 9,639 blocks
==14196==         suppressed: 0 bytes in 0 blocks
==14196== Rerun with --leak-check=full to see details of leaked memory
==14196== 
==14196== For counts of detected and suppressed errors, rerun with: -v
==14196== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

[ no debug trace ]

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