wnpa-sec-2017-13 · WBXML dissector infinite loop

Summary

Name: WBXML dissector infinite loop

Docid: wnpa-sec-2017-13

Date: April 12, 2017

Affected versions: 2.2.0 to 2.2.7, 2.0.0 to 2.0.13

Fixed versions: 2.2.8, 2.0.14

References:
Wireshark bug 13477
Wireshark bug 13796
CVE-2017-7702
CVE-2017-11410

Details

Description

The WBXML dissector could go into an infinite loop. Discovered by Otto Airamo and Antti Levomäki, Forcepoint.

Impact

It may be possible to make Wireshark consume excessive CPU resources by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file.

Resolution

Upgrade to Wireshark 2.2.8, 2.0.14 or later.

Update: July 18, 2017

Updated for Wireshark 2.2.8 and 2.0.14. Added bug 13796.
Go Beyond with Riverbed Technology

Riverbed is Wireshark's primary sponsor and provides our funding. They also make great products that fully integrate with Wireshark.

I have a lot of traffic...

ANSWER: SteelCentral™ Packet Analyzer PE
  • • Visually rich, powerful LAN analyzer
  • • Quickly access very large pcap files
  • • Professional, customizable reports
  • • Advanced triggers and alerts
  • • Fully integrated with Wireshark and AirPcap™
Learn More

Buy Now

No, really, I have a LOT of traffic…

ANSWER: SteelCentral™ NetShark appliance
  • • Troubleshoot problems faster
  • • Quickly identify the applications running on your network
  • • Monitor your virtual machine traffic
Learn More

I need to capture wireless traffic...

ANSWER: AirPcap™ 802.11 Packet Capture
  • • WLAN packet capture and transmission
  • • Full 802.11 a/b/g/n support
  • • View management, control and data frames
  • • Multi-channel aggregation (with multiple adapters)
Learn More Buy Now