CVE-2017-9347: Null Pointer Dereference

Published Jun 2, 2017
·
Updated

In Wireshark 2.2.0 to 2.2.6, the ROS dissector could crash with a NULL pointer dereference. This was addressed in epan/dissectors/asn1/ros/packet-ros-template.c by validating an OID.

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-9347?

CVE-2017-9347 has been classified with a high severity rating due to the potential for crashing the Wireshark application.

2

How do I fix CVE-2017-9347?

To fix CVE-2017-9347, upgrade Wireshark to version 2.2.7 or later, where the issue has been addressed.

3

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

Wireshark versions 2.2.0 through 2.2.6 are affected by CVE-2017-9347.

4

What happens if I don't address CVE-2017-9347?

Failing to address CVE-2017-9347 may result in system instability and crashes while using Wireshark.

5

Is there any workaround for CVE-2017-9347?

There are no known workarounds for CVE-2017-9347; the recommended action is to update 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