In Wireshark 2.2.0 to 2.2.1 and 2.0.0 to 2.0.7, the AllJoyn dissector could crash with a buffer over-read, triggered by network traffic or a capture file. This was addressed in epan/dissectors/packet-alljoyn.c by ensuring that a length variable properly tracked the state of a signature variable.
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
| Link | Tags |
|---|---|
| https://www.wireshark.org/security/wnpa-sec-2016-59.html | vendor advisory |
| https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=a5770b6559b6e6765c4ef800e85ae42781ea4900 | |
| http://www.securitytracker.com/id/1037313 | vdb entry |
| http://www.debian.org/security/2016/dsa-3719 | third party advisory vendor advisory |
| https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12953 | issue tracking |
| http://www.securityfocus.com/bid/94369 | vdb entry third party advisory |