In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the DHCP dissector could read past the end of a buffer. This was addressed in epan/dissectors/packet-bootp.c by extracting the Vendor Class Identifier more carefully.
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://bugs.chromium.org/p/oss-fuzz/issues/detail?id=1183 | third party advisory issue tracking |
| https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=1153 | third party advisory issue tracking |
| http://www.securityfocus.com/bid/98808 | third party advisory vdb entry |
| https://www.wireshark.org/security/wnpa-sec-2017-24.html | vendor advisory |
| https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13609 | patch vendor advisory issue tracking |
| https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=a6e033c14da13bd5f72dfe07a347586517639d12 | |
| http://www.securitytracker.com/id/1038612 | third party advisory vdb entry |
| https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13628 | patch vendor advisory issue tracking |