In Wireshark 2.2.0 to 2.2.1 and 2.0.0 to 2.0.7, the DCERPC dissector could crash with a use-after-free, triggered by network traffic or a capture file. This was addressed in epan/dissectors/packet-dcerpc-nt.c and epan/dissectors/packet-dcerpc-spoolss.c by using the wmem file scope for private strings.
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
| Link | Tags |
|---|---|
| http://www.securitytracker.com/id/1037313 | vdb entry |
| https://www.wireshark.org/security/wnpa-sec-2016-61.html | vendor advisory |
| https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=cc8e37f0f53c4401bb1644a34eddea345940a8df | |
| http://www.debian.org/security/2016/dsa-3719 | third party advisory vendor advisory |
| https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13072 | issue tracking |
| http://www.securityfocus.com/bid/94369 | vdb entry third party advisory |