| Bug ID |
9031
|
| Summary |
Wireshark fails to decode single-line, multiple Contact: URIs in SIP responses
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.10.1
|
| Hardware |
x86-64
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Minor
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 11364 [details]
Capture file with bug as example.
Build Information:
Version 1.10.1 (SVN Rev 50926 from /trunk-1.10)
Afaik: The same bug is also available in 1.8.x
--
When wireshark decodes an 200 OK response with multiple contacts, it fails to
separate multiple URIs in a single Contact-header (separated with COMMA), into
indivual contact-header instances.
Such as:
Contact: <sip:[email protected]:55812>;expires=887,
<sip:[email protected]:53155>;expires=900
Should be interpreted as:
Contact: URI1
Contact: URI2
This causes the GUI to display "1 bindings", when there are actually more than
one.
You are receiving this mail because:
- You are watching all bug changes.