In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the openSAFETY dissector could crash or exhaust system memory. This was addressed in epan/dissectors/packet-opensafety.c by checking for a negative length.
References
Link | Resource |
---|---|
https://www.wireshark.org/security/wnpa-sec-2017-28.html | Vendor Advisory |
https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=dbc7cb0bbdd501fa96e0cb98668f6d6bf17ac4e6 | Issue Tracking Patch Vendor Advisory |
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13649 | Issue Tracking Patch Vendor Advisory |
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=1212 | Issue Tracking Third Party Advisory |
http://www.securityfocus.com/bid/98806 | Third Party Advisory VDB Entry |
http://www.securitytracker.com/id/1038612 | Third Party Advisory VDB Entry |
Configurations
Configuration 1 (hide)
|
Information
Published : 2017-06-01 22:29
Updated : 2019-10-02 17:03
NVD link : CVE-2017-9350
Mitre link : CVE-2017-9350
JSON object : View
Products Affected
wireshark
- wireshark