| Bug ID |
9883
|
| Summary |
Buildbot crash output: fuzz-2014-03-12-27677.pcap
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86-64
|
| URL |
http://www.wireshark.org/download/automated/captures/fuzz-2014-03-12-27677.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:
http://www.wireshark.org/download/automated/captures/fuzz-2014-03-12-27677.pcap
stderr:
Input file: /home/wireshark/menagerie/menagerie/7274-bug6469_gsmfillbits.pcap
Build host information:
Linux wsbb04 3.2.0-60-generic #91-Ubuntu SMP Wed Feb 19 03:54:44 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 12.04.4 LTS
Release: 12.04
Codename: precise
Buildbot information:
BUILDBOT_REPOSITORY=ssh://[email protected]:29418/wireshark
BUILDBOT_BUILDNUMBER=2633
BUILDBOT_URL=http://buildbot.wireshark.org/trunk/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_SLAVENAME=clang-code-analysis
BUILDBOT_GOT_REVISION=7e7bf824564ab936fd2aafba269b4d73e406aa48
Return value: 139
Dissector bug: 0
Valgrind error count: 0
Git commit
commit 7e7bf824564ab936fd2aafba269b4d73e406aa48
Author: Hadriel Kaplan <[email protected]>
Date: Tue Mar 11 22:27:42 2014 -0400
Fix Bug 9872: 'SIP status line in 200 OK for de-registration is misleading'
The status line of the 200 OK during a deregistration is (1 bindings), but
it
should be (0 bindings). Wireshark should check the "expires=0" in the
contact
header not just count the number of the contact lines. But since it's not
truly valid to have expires=o contacts in responses, this commit adds
expert
info warning of such.
Also, the REGISTER request itself already says "(remove all bindings)"
in the Info column currently if the Contact was a '*', but it didn't
say something similar if only de-registering one or more explicit
contacts. This has been fixed as well.
Lastly, this fixes three other bugs I found while reading the code and
testing:
(1) comma-separated Contact headers will be displayed as a single one if
the first one(s) don't have header params but a subsequent one does; and
(2) the last Contact header param is displayed with the trailing '\r\n'
header separator; and (3) the SIP REGISTER response code displayed contact
binding info for responses other than 2xx, which isn't logical.
Since all of these are in the same area and not critical, I'm lumping these
all together.
A test capture file used for testing is attached to the bug.
As an aside, the SIP header parsing code needs to be refactored. Most SIP
headers follow a common ABNF pattern, and should be parsed using a common
function(s) so these issues don't crop up for specific headers.
Change-Id: I16c531fcb244dc121fc0e8046908e475b41489f9
Reviewed-on: https://code.wireshark.org/review/612
Reviewed-by: Anders Broman <[email protected]>
Reviewed-by: Alexis La Goutte <[email protected]>
Tested-by: Alexis La Goutte <[email protected]>
Command and args: ./tshark -nVxr
[ no debug trace ]
You are receiving this mail because:
- You are watching all bug changes.
