CVE-2011-1957: Medium severity wireshark vulnerability

Published Jun 2, 2011
·
Updated

It was found that Wireshark's DICOM dissector did not check for invalid payload data unit length. A remote attacker could create a specially-crafted capture file, which once opened, by a local, unsuspecting user could lead to wireshark application hang / termination.

References: [1] https://bugs.wireshark.org/bugzilla/showbug.cgi?id=5876 (upstream bug report) [2] http://www.wireshark.org/download/automated/captures/fuzz-2011-04-30-7272.pcap (public reproducer) [3] http://www.openwall.com/lists/oss-security/2011/05/31/20 (CVE request) [4] http://www.wireshark.org/security/wnpa-sec-2011-07.html (upstream advisory)

Upstream patch: [5] http://anonsvn.wireshark.org/viewvc?view=revision&revision=36958

Other sources

The dissectdcmmain function in epan/dissectors/packet-dcm.c in the DICOM dissector in Wireshark 1.2.x before 1.2.17 and 1.4.x before 1.4.7 allows remote attackers to cause a denial of service (infinite loop) via an invalid PDU length.

MITRE

Affected Software

25 affected components
Wireshark Wireshark=1.2
Wireshark Wireshark=1.2.0
Wireshark Wireshark=1.2.1
Wireshark Wireshark=1.2.2
Wireshark Wireshark=1.2.3
Wireshark Wireshark=1.2.4
Wireshark Wireshark=1.2.5
Wireshark Wireshark=1.2.6
Wireshark Wireshark=1.2.7
Wireshark Wireshark=1.2.8
Wireshark Wireshark=1.2.9
Wireshark Wireshark=1.2.10
Wireshark Wireshark=1.2.11
Wireshark Wireshark=1.2.12
Wireshark Wireshark=1.2.13
Wireshark Wireshark=1.2.14
Wireshark Wireshark=1.2.15
Wireshark Wireshark=1.2.16
Wireshark Wireshark=1.4.0
Wireshark Wireshark=1.4.1
Wireshark Wireshark=1.4.2
Wireshark Wireshark=1.4.3
Wireshark Wireshark=1.4.4
Wireshark Wireshark=1.4.5
Wireshark Wireshark=1.4.6

Event History

Jun 2, 2011
Data Sourced
09:42 AM
DescriptionSeverityAffected Software
Jun 6, 2011
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2011-1957?

CVE-2011-1957 has a medium severity level as it can lead to application hang or termination.

2

How do I fix CVE-2011-1957?

To fix CVE-2011-1957, update Wireshark to a version later than 1.2.16.

3

Which versions of Wireshark are affected by CVE-2011-1957?

CVE-2011-1957 affects Wireshark versions 1.2.0 through 1.2.16.

4

What kind of attack is possible with CVE-2011-1957?

An attacker can create a specially-crafted capture file that, when opened, can cause Wireshark to hang or terminate.

5

Is CVE-2011-1957 a remote vulnerability?

Yes, CVE-2011-1957 can be exploited remotely by using a malicious capture file.

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