ArchLinux: 201812-3: wireshark-cli: multiple issues
Summary
- CVE-2018-19622 (denial of service)
A security issue has been found in the MMSE dissector of Wireshark
versions prior to 2.6.5, which could be made to consume excessive CPU
resources by injecting a malformed packet onto the wire or by
convincing someone to read a malformed packet trace file
- CVE-2018-19623 (arbitrary code execution)
A heap-based out-of-bounds write has been found in the LBMPDM dissector
of Wireshark versions prior to 2.6.5, which could be triggered by
injecting a malformed packet onto the wire or by convincing someone to
read a malformed packet trace file
- CVE-2018-19624 (denial of service)
A NULL-pointer dereference has been found in the PVFS dissector of
Wireshark versions prior to 2.6.5, which could be triggered by
injecting a malformed packet onto the wire or by convincing someone to
read a malformed packet trace file
- CVE-2018-19625 (information disclosure)
An out-of-bounds read has been found in the dissection engine of
Wireshark versions prior to 2.6.5, which could be triggered by
injecting a malformed packet onto the wire or by convincing someone to
read a malformed packet trace file
- CVE-2018-19626 (information disclosure)
An out-of-bounds read has been found in the DCOM dissector of Wireshark
versions prior to 2.6.5, which could be triggered by injecting a
malformed packet onto the wire or by convincing someone to read a
malformed packet trace file
- CVE-2018-19627 (information disclosure)
An out-of-bounds read has been found in the IxVeriWave file parser of
Wireshark versions prior to 2.6.5, which could be triggered by
injecting a malformed packet onto the wire or by convincing someone to
read a malformed packet trace file
- CVE-2018-19628 (denial of service)
A divide-by-zero error has been found in the ZigBee ZCL dissector of
Wireshark versions prior to 2.6.5, which could be triggered by
injecting a malformed packet onto the wire or by convincing someone to
read a malformed packet trace file
Resolution
Upgrade to 2.6.5-1.
# pacman -Syu "wireshark-cli>=2.6.5-1"
The problems have been fixed upstream in version 2.6.5.
References
https://www.wireshark.org/docs/relnotes/wireshark-2.6.5.html https://www.wireshark.org/security/wnpa-sec-2018-54 https://gitlab.com/wireshark/wireshark/-/issues/15250 https://www.wireshark.org/security/wnpa-sec-2018-53 https://gitlab.com/wireshark/wireshark/-/issues/15132 https://www.wireshark.org/security/wnpa-sec-2018-56 https://gitlab.com/wireshark/wireshark/-/issues/15280 https://www.wireshark.org/security/wnpa-sec-2018-51 https://gitlab.com/wireshark/wireshark/-/issues/14466 https://www.wireshark.org/security/wnpa-sec-2018-52 https://gitlab.com/wireshark/wireshark/-/issues/15130 https://www.wireshark.org/security/wnpa-sec-2018-55 https://gitlab.com/wireshark/wireshark/-/issues/15279 https://www.wireshark.org/security/wnpa-sec-2018-57 https://gitlab.com/wireshark/wireshark/-/issues/15281 https://security.archlinux.org/CVE-2018-19622 https://security.archlinux.org/CVE-2018-19623 https://security.archlinux.org/CVE-2018-19624 https://security.archlinux.org/CVE-2018-19625 https://security.archlinux.org/CVE-2018-19626 https://security.archlinux.org/CVE-2018-19627 https://security.archlinux.org/CVE-2018-19628
Workaround
None.