CVE-2017-9353: Input Validation

Published Jun 2, 2017
·
Updated

In Wireshark 2.2.0 to 2.2.6, the IPv6 dissector could crash. This was addressed in epan/dissectors/packet-ipv6.c by validating an IPv6 address.

Affected Software

21 affected componentsFixes available
Wireshark Wireshark>=2.2.0<=2.2.6
alpine/wireshark>=2.2.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.2.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.2.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.2.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.2.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.2.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.2.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.2.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.2.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.2.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.2.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.2.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.2.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.2.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.2.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.2.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.2.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.2.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.2.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.2.0<2.2.7-r0
2.2.7-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade alpine/wireshark to a version that resolves this vulnerability.

    Fixed in 2.2.7-r0

Event History

Jun 2, 2017
CVE Published
via MITRE·05:04 AM
Data Sourced
via MITRE·05:04 AM
Description
Data Sourced
via NVD·05:29 AM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·05:29 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2017-9353?

CVE-2017-9353 has been rated as a medium severity vulnerability due to its potential to cause application crashes.

2

How do I fix CVE-2017-9353?

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

3

What software versions are affected by CVE-2017-9353?

CVE-2017-9353 affects Wireshark versions from 2.2.0 to 2.2.6.

4

Who discovered the vulnerability CVE-2017-9353?

CVE-2017-9353 was discovered through a fuzzing initiative that aimed to identify potential security issues in Wireshark.

5

What component of Wireshark is impacted by CVE-2017-9353?

CVE-2017-9353 impacts the IPv6 dissector component of Wireshark.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203