In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the BGP dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-bgp.c by using a different integer data type.

Am I vulnerable?

The constraints below list the versions that this vulnerability is patched in, and versions that are unaffected. If a patch is ready but unrealeased, then it is pending.

Or, you can just let us figure it out for you! Appcanary continously monitor your installed packages, and tell you if any of them are vulnerable.

Sign up for monitoring

Affected package information

Release Package Patched in
artful wireshark 2.2.6+g32dac6a-2
devel wireshark 2.2.6+g32dac6a-2
upstream wireshark 2.2.6,2.0.12
xenial wireshark 2.2.6+g32dac6a-2ubuntu0.16.04
yakkety wireshark 2.2.6+g32dac6a-2ubuntu0.16.10
zesty wireshark 2.2.6+g32dac6a-2ubuntu0.17.04


Release Package Reason
precise wireshark ignored
precise/esm wireshark DNE
vivid/stable-phone-overlay wireshark DNE
vivid/ubuntu-core wireshark DNE

Needs Triage

Release Package Reason
trusty wireshark needs-triage