In Wireshark 2.2.4 and earlier, a crafted or malformed STANAG 4607 capture file will cause an infinite loop and memory exhaustion. If the packet size field in a packet header is null, the offset to read from will not advance, causing continuous attempts to read the same zero length packet. This will quickly exhaust all system memory. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-6014 https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13416
Arch teams, please test and mark stable: =net-analyzer/wireshark-2.2.5 Targeted stable KEYWORDS : alpha amd64 arm hppa ia64 ppc ppc64 sparc x86
Stable for HPPA PPC64.
Stable on alpha.
arm stable
amd64 stable
x86 stable
sparc stable
ppc stable.
ia64 stable. Maintainer(s), please cleanup. Security, please vote.
(In reply to Michael Weber from comment #8) > ppc stable. That didn't actually happen.
Arches and Maintainer(s), Thank you for your work. New GLSA Request filed.
This issue was resolved and addressed in GLSA 201706-12 at https://security.gentoo.org/glsa/201706-12 by GLSA coordinator Kristian Fiskerstrand (K_F).