What is the severity of CVE-2016-7957?

CVE-2016-7957 has been classified as a high severity vulnerability due to the potential for application crashes.

How do I fix CVE-2016-7957?

To fix CVE-2016-7957, upgrade Wireshark to version 2.2.1 or later, where this vulnerability has been addressed.

What versions of Wireshark are affected by CVE-2016-7957?

CVE-2016-7957 specifically affects Wireshark version 2.2.0.

What attack vectors can trigger CVE-2016-7957?

CVE-2016-7957 can be triggered by packet injection or a malformed capture file.

What component of Wireshark does CVE-2016-7957 involve?

CVE-2016-7957 involves the Bluetooth L2CAP dissector within Wireshark.

Vulnerability/
CVE-2016-7957

high

7.5

CWE

12/4/2017

6/8/2024

CVE-2016-7957: Input Validation

First published: Wed Apr 12 2017(Updated: )

In Wireshark 2.2.0, the Bluetooth L2CAP dissector could crash, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-btl2cap.c by avoiding use of a seven-byte memcmp for potentially shorter strings.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Wireshark Wireshark	=2.2.0

Remedy

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12825

Remedy

https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=355b56b1c6c545072ac0c1225730b526c6749f0a

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-7957?
CVE-2016-7957 has been classified as a high severity vulnerability due to the potential for application crashes.
How do I fix CVE-2016-7957?
To fix CVE-2016-7957, upgrade Wireshark to version 2.2.1 or later, where this vulnerability has been addressed.
What versions of Wireshark are affected by CVE-2016-7957?
CVE-2016-7957 specifically affects Wireshark version 2.2.0.
What attack vectors can trigger CVE-2016-7957?
CVE-2016-7957 can be triggered by packet injection or a malformed capture file.
What component of Wireshark does CVE-2016-7957 involve?
CVE-2016-7957 involves the Bluetooth L2CAP dissector within Wireshark.

collector/nvd-index
agent/type
agent/softwarecombine
agent/remedy
collector/mitre-cve
source/MITRE
agent/severity
agent/author
agent/last-modified-date
agent/weakness
agent/references
agent/description
agent/first-publish-date
agent/event
agent/tags
agent/source
vendor/wireshark
canonical/wireshark wireshark
version/wireshark wireshark/2.2.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2016-7957?
CVE-2016-7957 has been classified as a high severity vulnerability due to the potential for application crashes.
How do I fix CVE-2016-7957?
To fix CVE-2016-7957, upgrade Wireshark to version 2.2.1 or later, where this vulnerability has been addressed.
What versions of Wireshark are affected by CVE-2016-7957?
CVE-2016-7957 specifically affects Wireshark version 2.2.0.
What attack vectors can trigger CVE-2016-7957?
CVE-2016-7957 can be triggered by packet injection or a malformed capture file.
What component of Wireshark does CVE-2016-7957 involve?
CVE-2016-7957 involves the Bluetooth L2CAP dissector within Wireshark.