What is the severity of CVE-2017-11407?

CVE-2017-11407 is categorized as a medium severity vulnerability due to the potential crash of the application.

How do I fix CVE-2017-11407?

To fix CVE-2017-11407, upgrade Wireshark to versions 2.2.8 or higher and 2.0.14 or higher.

Which versions of Wireshark are affected by CVE-2017-11407?

Wireshark versions 2.0.0 to 2.0.13 and 2.2.0 to 2.2.7 are affected by CVE-2017-11407.

What component of Wireshark is affected by CVE-2017-11407?

CVE-2017-11407 specifically affects the MQ dissector in Wireshark.

What impact does CVE-2017-11407 have on system stability?

CVE-2017-11407 can cause Wireshark to crash, potentially leading to loss of unsaved work or data.

Vulnerability/
CVE-2017-11407

high

7.5

CWE

18/7/2017

1/3/2019

CVE-2017-11407: Input Validation

First published: Tue Jul 18 2017(Updated: )

In Wireshark 2.2.0 to 2.2.7 and 2.0.0 to 2.0.13, the MQ dissector could crash. This was addressed in epan/dissectors/packet-mq.c by validating the fragment length before a reassembly attempt.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Wireshark Wireshark	>=2.0.0<=2.0.13
Wireshark Wireshark	>=2.2.0<=2.2.7
Debian GNU/Linux	=8.0

Remedy

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

Remedy

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

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-11407?
CVE-2017-11407 is categorized as a medium severity vulnerability due to the potential crash of the application.
How do I fix CVE-2017-11407?
To fix CVE-2017-11407, upgrade Wireshark to versions 2.2.8 or higher and 2.0.14 or higher.
Which versions of Wireshark are affected by CVE-2017-11407?
Wireshark versions 2.0.0 to 2.0.13 and 2.2.0 to 2.2.7 are affected by CVE-2017-11407.
What component of Wireshark is affected by CVE-2017-11407?
CVE-2017-11407 specifically affects the MQ dissector in Wireshark.
What impact does CVE-2017-11407 have on system stability?
CVE-2017-11407 can cause Wireshark to crash, potentially leading to loss of unsaved work or data.

agent/references
agent/last-modified-date
agent/remedy
agent/type
agent/severity
agent/weakness
agent/author
agent/description
agent/first-publish-date
agent/event
agent/tags
agent/softwarecombine
collector/nvd-index
agent/software-canonical-lookup-request
vendor/wireshark
canonical/wireshark wireshark
version/wireshark wireshark/2.0.0
version/wireshark wireshark/2.0.13
version/wireshark wireshark/2.2.0
version/wireshark wireshark/2.2.7
vendor/debian
canonical/debian gnu/linux
version/debian gnu/linux/8.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-2017-11407?
CVE-2017-11407 is categorized as a medium severity vulnerability due to the potential crash of the application.
How do I fix CVE-2017-11407?
To fix CVE-2017-11407, upgrade Wireshark to versions 2.2.8 or higher and 2.0.14 or higher.
Which versions of Wireshark are affected by CVE-2017-11407?
Wireshark versions 2.0.0 to 2.0.13 and 2.2.0 to 2.2.7 are affected by CVE-2017-11407.
What component of Wireshark is affected by CVE-2017-11407?
CVE-2017-11407 specifically affects the MQ dissector in Wireshark.
What impact does CVE-2017-11407 have on system stability?
CVE-2017-11407 can cause Wireshark to crash, potentially leading to loss of unsaved work or data.