In Wireshark 2.2.0 to 2.2.4 and 2.0.0 to 2.0.10, there is a WSP infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-wsp.c by validating the capability length.
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
Alpine | edge-community | noarch | wireshark | < 2.2.5-r0 | UNKNOWN |
Alpine | 3.10-community | noarch | wireshark | < 2.2.5-r0 | UNKNOWN |
Alpine | 3.11-community | noarch | wireshark | < 2.2.5-r0 | UNKNOWN |
Alpine | 3.12-community | noarch | wireshark | < 2.2.5-r0 | UNKNOWN |
Alpine | 3.13-community | noarch | wireshark | < 2.2.5-r0 | UNKNOWN |
Alpine | 3.14-community | noarch | wireshark | < 2.2.5-r0 | UNKNOWN |
Alpine | 3.15-community | noarch | wireshark | < 2.2.5-r0 | UNKNOWN |
Alpine | 3.16-community | noarch | wireshark | < 2.2.5-r0 | UNKNOWN |
Alpine | 3.17-community | noarch | wireshark | < 2.2.5-r0 | UNKNOWN |
Alpine | 3.18-community | noarch | wireshark | < 2.2.5-r0 | UNKNOWN |