What is the severity of CVE-2017-9352?

CVE-2017-9352 has been classified as a medium severity vulnerability.

How do I fix CVE-2017-9352?

To fix CVE-2017-9352, upgrade Wireshark to version 2.2.7 or later, or 2.0.13 or later.

What versions of Wireshark are affected by CVE-2017-9352?

CVE-2017-9352 affects Wireshark versions 2.0.0 to 2.0.12 and 2.2.0 to 2.2.6.

What is the impact of CVE-2017-9352?

The vulnerability can cause Wireshark to enter an infinite loop, potentially leading to a denial of service.

Who discovered CVE-2017-9352?

CVE-2017-9352 was reported by security researchers analyzing the Bazaar dissector in Wireshark.

Vulnerability/
CVE-2017-9352

high

7.8

CWE

835

2/6/2017

3/10/2019

CVE-2017-9352

First published: Fri Jun 02 2017(Updated: )

In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the Bazaar dissector could go into an infinite loop. This was addressed in epan/dissectors/packet-bzr.c by ensuring that backwards parsing cannot occur.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Wireshark Wireshark	>=2.0.0<=2.0.12
Wireshark Wireshark	>=2.2.0<=2.2.6

Remedy

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

Remedy

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

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-9352?
CVE-2017-9352 has been classified as a medium severity vulnerability.
How do I fix CVE-2017-9352?
To fix CVE-2017-9352, upgrade Wireshark to version 2.2.7 or later, or 2.0.13 or later.
What versions of Wireshark are affected by CVE-2017-9352?
CVE-2017-9352 affects Wireshark versions 2.0.0 to 2.0.12 and 2.2.0 to 2.2.6.
What is the impact of CVE-2017-9352?
The vulnerability can cause Wireshark to enter an infinite loop, potentially leading to a denial of service.
Who discovered CVE-2017-9352?
CVE-2017-9352 was reported by security researchers analyzing the Bazaar dissector in Wireshark.

collector/nvd-index
agent/weakness
agent/references
agent/severity
agent/author
agent/description
agent/tags
agent/type
agent/event
agent/remedy
agent/last-modified-date
agent/softwarecombine
agent/first-publish-date
vendor/wireshark
canonical/wireshark wireshark
version/wireshark wireshark/2.0.0
version/wireshark wireshark/2.0.12
version/wireshark wireshark/2.2.0
version/wireshark wireshark/2.2.6

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-2017-9352?
CVE-2017-9352 has been classified as a medium severity vulnerability.
How do I fix CVE-2017-9352?
To fix CVE-2017-9352, upgrade Wireshark to version 2.2.7 or later, or 2.0.13 or later.
What versions of Wireshark are affected by CVE-2017-9352?
CVE-2017-9352 affects Wireshark versions 2.0.0 to 2.0.12 and 2.2.0 to 2.2.6.
What is the impact of CVE-2017-9352?
The vulnerability can cause Wireshark to enter an infinite loop, potentially leading to a denial of service.
Who discovered CVE-2017-9352?
CVE-2017-9352 was reported by security researchers analyzing the Bazaar dissector in Wireshark.