What is the severity of CVE-2016-2528?

CVE-2016-2528 has a high severity rating due to its potential to cause a denial of service through stack-based buffer overflow.

How do I fix CVE-2016-2528?

To fix CVE-2016-2528, upgrade Wireshark to version 2.0.2 or later, which addresses the vulnerability.

Who is affected by CVE-2016-2528?

CVE-2016-2528 affects users of Wireshark versions 2.0.0 and 2.0.1.

What type of attack does CVE-2016-2528 enable?

CVE-2016-2528 enables remote attackers to conduct denial of service attacks resulting in application crashes.

What component of Wireshark is vulnerable in CVE-2016-2528?

CVE-2016-2528 is related to the LBMC dissector in the Wireshark application.

Vulnerability/
CVE-2016-2528

medium

5.9

CWE

20 119

28/2/2016

5/8/2024

CVE-2016-2528: Input Validation

First published: Sun Feb 28 2016(Updated: )

The dissect_nhdr_extopt function in epan/dissectors/packet-lbmc.c in the LBMC dissector in Wireshark 2.0.x before 2.0.2 does not validate length values, which allows remote attackers to cause a denial of service (stack-based buffer overflow and application crash) via a crafted packet.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Wireshark Wireshark	=2.0.0
Wireshark Wireshark	=2.0.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-2528?
CVE-2016-2528 has a high severity rating due to its potential to cause a denial of service through stack-based buffer overflow.
How do I fix CVE-2016-2528?
To fix CVE-2016-2528, upgrade Wireshark to version 2.0.2 or later, which addresses the vulnerability.
Who is affected by CVE-2016-2528?
CVE-2016-2528 affects users of Wireshark versions 2.0.0 and 2.0.1.
What type of attack does CVE-2016-2528 enable?
CVE-2016-2528 enables remote attackers to conduct denial of service attacks resulting in application crashes.
What component of Wireshark is vulnerable in CVE-2016-2528?
CVE-2016-2528 is related to the LBMC dissector in the Wireshark application.

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

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-2528?
CVE-2016-2528 has a high severity rating due to its potential to cause a denial of service through stack-based buffer overflow.
How do I fix CVE-2016-2528?
To fix CVE-2016-2528, upgrade Wireshark to version 2.0.2 or later, which addresses the vulnerability.
Who is affected by CVE-2016-2528?
CVE-2016-2528 affects users of Wireshark versions 2.0.0 and 2.0.1.
What type of attack does CVE-2016-2528 enable?
CVE-2016-2528 enables remote attackers to conduct denial of service attacks resulting in application crashes.
What component of Wireshark is vulnerable in CVE-2016-2528?
CVE-2016-2528 is related to the LBMC dissector in the Wireshark application.