What is the severity of CVE-2016-6513?

CVE-2016-6513 has been classified as a denial of service vulnerability that can cause application crashes.

How do I fix CVE-2016-6513?

To fix CVE-2016-6513, upgrade Wireshark to version 2.0.5 or later.

What software versions are affected by CVE-2016-6513?

Wireshark versions 2.0.0 to 2.0.4 are affected by CVE-2016-6513.

Who is impacted by CVE-2016-6513?

Users of Wireshark versions 2.0.0 to 2.0.4 may be impacted by CVE-2016-6513 if they process crafted packets.

What is the nature of the attack in CVE-2016-6513?

The attack in CVE-2016-6513 involves sending crafted WBXML packets that exploit the lack of recursion depth restriction, leading to application crashes.

Vulnerability/
CVE-2016-6513

medium

5.9

CWE

399

6/8/2016

6/8/2024

CVE-2016-6513

First published: Sat Aug 06 2016(Updated: )

epan/dissectors/packet-wbxml.c in the WBXML dissector in Wireshark 2.x before 2.0.5 does not restrict the recursion depth, which allows remote attackers to cause a denial of service (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
Wireshark Wireshark	=2.0.2
Wireshark Wireshark	=2.0.3
Wireshark Wireshark	=2.0.4

Remedy

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

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-6513?
CVE-2016-6513 has been classified as a denial of service vulnerability that can cause application crashes.
How do I fix CVE-2016-6513?
To fix CVE-2016-6513, upgrade Wireshark to version 2.0.5 or later.
What software versions are affected by CVE-2016-6513?
Wireshark versions 2.0.0 to 2.0.4 are affected by CVE-2016-6513.
Who is impacted by CVE-2016-6513?
Users of Wireshark versions 2.0.0 to 2.0.4 may be impacted by CVE-2016-6513 if they process crafted packets.
What is the nature of the attack in CVE-2016-6513?
The attack in CVE-2016-6513 involves sending crafted WBXML packets that exploit the lack of recursion depth restriction, leading to application crashes.

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

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-6513?
CVE-2016-6513 has been classified as a denial of service vulnerability that can cause application crashes.
How do I fix CVE-2016-6513?
To fix CVE-2016-6513, upgrade Wireshark to version 2.0.5 or later.
What software versions are affected by CVE-2016-6513?
Wireshark versions 2.0.0 to 2.0.4 are affected by CVE-2016-6513.
Who is impacted by CVE-2016-6513?
Users of Wireshark versions 2.0.0 to 2.0.4 may be impacted by CVE-2016-6513 if they process crafted packets.
What is the nature of the attack in CVE-2016-6513?
The attack in CVE-2016-6513 involves sending crafted WBXML packets that exploit the lack of recursion depth restriction, leading to application crashes.