Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Summary

Name:Multiple vulnerabilities in Wireshark® version 0.9.2 to 1.2.0

Docid: wnpa-sec-2009-04

Date: July 20, 2009

Versions affected: 0.9.2 up to and including 1.2.0

Details

Description

Wireshark 1.2.1 fixes the following vulnerabilities:

  • The IPMI dissector could overrun a buffer. (Bug 3559)
    Versions affected: 1.2.0
    CVE-2009-2559
  • The AFS dissector could crash. (Bug 3564)
    Versions affected: 0.9.2 to 1.2.0
    CVE-2009-2562
  • The Infiniband dissector could crash on some platforms.
    Versions affected: 1.0.6 to 1.2.0
    CVE-2009-2563
  • The Bluetooth L2CAP dissector could crash. (Bug 3572)
    Versions affected: 1.2.0
    CVE-2009-2560
  • The RADIUS dissector could crash. (Bug 3578)
    Versions affected: 0.10.13 to 1.0.9, 1.2.0
    CVE-2009-2560
  • The MIOP dissector could crash. (Bug 3652)
    Versions affected: 1.2.0
    CVE-2009-2560
  • The sFlow dissector could use excessive CPU and memory. (Bug 3570)
    Versions affected: 1.2.0
    CVE-2009-2561

Impact

It may be possible to make Wireshark crash remotely or by convincing someone to read a malformed packet trace file.

Resolution

Upgrade to Wireshark 1.2.1 or later.

If are running Wireshark 1.2.0 or earlier (including Ethereal) and cannot upgrade, you can work around each of the problems listed above by doing the following:

  • Disable the affected dissectors:
    • Select Analyze→Enabled Protocols... from the menu.
    • Make sure "AFS (RX)", "Infiniband", "IPMI/ATCA", "L2CAP", "MIOP", "RADIUS", and "sFlow" are all un-checked.
    • Click "Save", then click "OK".

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation