CVE-2017-9349: High severity Wireshark Wireshark vulnerability

Published Jun 2, 2017
·
Updated

In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the DICOM dissector has an infinite loop. This was addressed in epan/dissectors/packet-dcm.c by validating a length value.

Affected Software

23 affected componentsFixes available
Wireshark Wireshark>=2.0.0<=2.0.12
Wireshark Wireshark>=2.2.0<=2.2.6
Debian Debian Linux=8.0
alpine/wireshark>=2.0.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.0.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.0.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.0.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.0.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.0.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.0.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.0.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.0.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.0.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.0.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.0.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.0.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.0.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.0.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.0.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.0.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.0.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.0.0<2.2.7-r0
2.2.7-r0
alpine/wireshark>=2.0.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-9349?

CVE-2017-9349 is classified as a moderate severity vulnerability due to the potential for denial-of-service from the infinite loop.

2

How do I fix CVE-2017-9349?

To fix CVE-2017-9349, upgrade Wireshark to a version later than 2.2.6 or 2.0.12.

3

What software is affected by CVE-2017-9349?

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

4

Is there a risk of exploitation for CVE-2017-9349?

Yes, CVE-2017-9349 can be exploited by sending specially crafted DICOM packets to trigger the infinite loop.

5

Who discovered CVE-2017-9349?

CVE-2017-9349 was reported through various security channels, including incident reports from security researchers.

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