CVE-2017-6014
In Wireshark 2.2.4 and earlier, a crafted or malformed STANAG 4607 capture file will cause an...
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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
7.5
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.
- Record
CVE-2017-6014- CVSS 3.0
- 7.5 High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - CVSS 2.0
- 7.8 High
AV:N/AC:L/Au:N/C:N/I:N/A:C - Weakness
- CWE-835
- Updated
- 2026-11-02
CVE List No score
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.
- Record
CVE-2017-6014- Updated
- 2026-11-02
EUVDEUVD-2017-15082 No score
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.
- Record
EUVD-2017-15082- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-8q6q-3849-7cm3
7.5
In Wireshark 2.2.4 and earlier, a crafted or malformed STANAG 4607 capture file will cause an...
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.
- Record
GHSA-8q6q-3849-7cm3- CVSS 3.0
- 7.5 High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-835
- Updated
- 2026-11-02
OSVALPINE-CVE-2017-6014
7.5
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.
- Record
ALPINE-CVE-2017-6014- CVSS 3.0
- 7.5 High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSV
7.5
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.
- Record
CVE-2017-6014- CVSS 3.0
- 7.5 High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
Show 5 moreShow less
OSVDEBIAN-CVE-2017-6014
7.5
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.
- Record
DEBIAN-CVE-2017-6014- CVSS 3.0
- 7.5 High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVUBUNTU-CVE-2017-6014
7.5
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.
- Record
UBUNTU-CVE-2017-6014- CVSS 3.0
- 7.5 High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVMGASA-2017-0076 No score
Updated wireshark packages fix security vulnerability
The wireshark package has been updated to version 2.0.11, which fixes two security issues where a malformed packet trace could cause it to crash or go into an infinite loop, and fixes several other bugs as well. See the release notes for details.
- Record
MGASA-2017-0076- Updated
- 2026-11-02
OSVSUSE-SU-2017:1174-1 No score
Security update for wireshark
Wireshark was updated to version 2.0.12, which brings several new features, enhancements and bug fixes.
These security issues were fixed:
- CVE-2017-7700: In Wireshark the NetScaler file parser could go into an infinite loop, triggered by a malformed capture file. This was addressed in wiretap/netscaler.c by ensuring a nonzero record size (bsc#1033936).
- CVE-2017-7701: In Wireshark 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 (bsc#1033937).
- CVE-2017-7702: In Wireshark the WBXML dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-wbxml.c by adding length validation (bsc#1033938).
- CVE-2017-7703: In Wireshark the IMAP dissector could crash, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-imap.c by calculating a line's end correctly (bsc#1033939).
- CVE-2017-7704: In Wireshark the DOF dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-dof.c by using a different integer data type and adjusting a return value (bsc#1033940).
- CVE-2017-7705: In Wireshark the RPC over RDMA dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-rpcrdma.c by correctly checking for going beyond the maximum offset (bsc#1033941).
- CVE-2017-7745: In Wireshark the SIGCOMP dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-sigcomp.c by correcting a memory-size check (bsc#1033942).
- CVE-2017-7746: In Wireshark the SLSK dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-slsk.c by adding checks for the remaining length (bsc#1033943).
- CVE-2017-7747: In Wireshark the PacketBB dissector could crash, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-packetbb.c by restricting additions to the protocol tree (bsc#1033944).
- CVE-2017-7748: In Wireshark the WSP dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-wsp.c by adding a length check (bsc#1033945).
- CVE-2016-7179: Stack-based buffer overflow in epan/dissectors/packet-catapult-dct2000.c in the Catapult DCT2000 dissector in Wireshark allowed remote attackers to cause a denial of service (application crash) via a crafted packet (bsc#998963).
- CVE-2016-9376: In Wireshark the OpenFlow dissector could crash with memory exhaustion, triggered by network traffic or a capture file. This was addressed in epan/dissectors/packet-openflow_v5.c by ensuring that certain length values were sufficiently large (bsc#1010735).
- CVE-2016-9375: In Wireshark the DTN dissector could go into an infinite loop, triggered by network traffic or a capture file. This was addressed in epan/dissectors/packet-dtn.c by checking whether SDNV evaluation was successful (bsc#1010740).
- CVE-2016-9374: In Wireshark the AllJoyn dissector could crash with a buffer over-read, triggered by network traffic or a capture file. This was addressed in epan/dissectors/packet-alljoyn.c by ensuring that a length variable properly tracked the state of a signature variable (bsc#1010752).
- CVE-2016-9373: In Wireshark the DCERPC dissector could crash with a use-after-free, triggered by network traffic or a capture file. This was addressed in epan/dissectors/packet-dcerpc-nt.c and epan/dissectors/packet-dcerpc-spoolss.c by using the wmem file scope for private strings (bsc#1010754).
- CVE-2016-7175: epan/dissectors/packet-qnet6.c in the…
- Record
SUSE-SU-2017:1174-1- Updated
- 2026-11-02
OSVSUSE-SU-2017:1442-1 No score
Security update for wireshark
Wireshark was updated to version 2.2.6, which brings several new features, enhancements and bug fixes.
Thses security issues were fixed:
- CVE-2017-7700: In Wireshark the NetScaler file parser could go into an infinite loop, triggered by a malformed capture file. This was addressed in wiretap/netscaler.c by ensuring a nonzero record size (bsc#1033936)
- CVE-2017-7701: In Wireshark 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 (bsc#1033937)
- CVE-2017-7702: In Wireshark the WBXML dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-wbxml.c by adding length validation (bsc#1033938)
- CVE-2017-7703: In Wireshark the IMAP dissector could crash, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-imap.c by calculating a line's end correctly (bsc#1033939)
- CVE-2017-7704: In Wireshark the DOF dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-dof.c by using a different integer data type and adjusting a return value (bsc#1033940)
- CVE-2017-7705: In Wireshark the RPC over RDMA dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-rpcrdma.c by correctly checking for going beyond the maximum offset (bsc#1033941)
- CVE-2017-7745: In Wireshark the SIGCOMP dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-sigcomp.c by correcting a memory-size check (bsc#1033942)
- CVE-2017-7746: In Wireshark the SLSK dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-slsk.c by adding checks for the remaining length (bsc#1033943)
- CVE-2017-7747: In Wireshark the PacketBB dissector could crash, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-packetbb.c by restricting additions to the protocol tree (bsc#1033944)
- CVE-2017-7748: In Wireshark the WSP dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-wsp.c by adding a length check (bsc#1033945)
- CVE-2017-6014: In Wireshark 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 (bsc#1025913)
- CVE-2017-5596: In Wireshark the ASTERIX dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-asterix.c by changing a data type to avoid an integer overflow (bsc#1021739)
- CVE-2017-5597: In Wireshark the DHCPv6 dissector could go into a large loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-dhcpv6.c by changing a data type to avoid an integer overflow (bsc#1021739)
- CVE-2016-9376: In Wireshark the OpenFlow dissector could crash with memory exhaustion, triggered by network traffic or a capture file. This was addressed in epan/dissectors/packet-openflow_v5.c by ensuring that certain length values were sufficiently large (bsc#1010735)
- CVE-2016-9375: In Wireshark the DTN dissector could go into an infinite loop, triggered by network traffic or a capture file. This was addressed in epan/dissectors/packet-dtn.c by checking whether SDNV evaluation was successful (bsc#1010740)
- CVE-2016-9374: In Wireshark the…
- Record
SUSE-SU-2017:1442-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
wiresharkAlpine:v3.5 |
before 2.2.4-r1 | 2.2.4-r1 |
wiresharkDebian:12 |
before 2.2.5+g440fd4d-2 | 2.2.5+g440fd4d-2 |
wiresharkDebian:13 |
before 2.2.5+g440fd4d-2 | 2.2.5+g440fd4d-2 |
wiresharkDebian:14 |
before 2.2.5+g440fd4d-2 | 2.2.5+g440fd4d-2 |
wiresharkDebian:7 |
before 1.12.1+g01b65bf-4+deb8u6~deb7u6, plus listed versions 1.10.0-11.10.0-21.10.0-2~bpo70+11.10.0~rc1-11.10.0~rc2-1 Show 45 moreShow less1.10.1-11.10.1-1~bpo70+11.10.2-11.10.2-1~bpo70+11.10.2-21.10.3-11.10.3-1~bpo70+11.10.4-11.10.5-11.10.5-1~bpo70+11.10.5-21.10.6-11.10.6-1~bpo70+11.10.7-11.10.7-1~bpo70+11.10.7-21.10.7-31.10.7-41.10.8-11.10.8-1~bpo70+11.12.0+git+4fab41a1-11.12.0~rc1-11.12.0~rc1-21.12.0~rc2+git+fd017ee+dfsg1-11.12.0~rc3+git+e14d5b6eaa+dfsg1-11.12.1+g01b65bf-11.12.1+g01b65bf-1~bpo70+11.12.1+g01b65bf-21.12.1+g01b65bf-2~bpo70+11.12.1+g01b65bf-31.12.1+g01b65bf-41.12.1+g01b65bf-4~bpo70+11.8.2-5wheezy101.8.2-5wheezy111.8.2-5wheezy121.8.2-5wheezy131.8.2-5wheezy141.8.2-5wheezy151.8.2-5wheezy15~deb6u11.8.2-5wheezy161.8.2-5wheezy16~deb6u11.8.2-5wheezy171.8.2-5wheezy181.8.2-5wheezy21.8.2-5wheezy3 |
1.12.1+g01b65bf-4+deb8u6~deb7u6 |
wiresharkDebian:8 From an advisory covering 11 CVEs |
before 1.12.1+g01b65bf-4+deb8u11, plus listed versions 1.12.1+g01b65bf-41.12.1+g01b65bf-4+deb8u11.12.1+g01b65bf-4+deb8u101.12.1+g01b65bf-4+deb8u21.12.1+g01b65bf-4+deb8u3 Show 17 moreShow less1.12.1+g01b65bf-4+deb8u41.12.1+g01b65bf-4+deb8u51.12.1+g01b65bf-4+deb8u61.12.1+g01b65bf-4+deb8u6~deb7u11.12.1+g01b65bf-4+deb8u6~deb7u101.12.1+g01b65bf-4+deb8u6~deb7u111.12.1+g01b65bf-4+deb8u6~deb7u21.12.1+g01b65bf-4+deb8u6~deb7u31.12.1+g01b65bf-4+deb8u6~deb7u41.12.1+g01b65bf-4+deb8u6~deb7u51.12.1+g01b65bf-4+deb8u6~deb7u61.12.1+g01b65bf-4+deb8u6~deb7u71.12.1+g01b65bf-4+deb8u6~deb7u81.12.1+g01b65bf-4+deb8u6~deb7u91.12.1+g01b65bf-4+deb8u71.12.1+g01b65bf-4+deb8u81.12.1+g01b65bf-4+deb8u9 |
1.12.1+g01b65bf-4+deb8u11 |
wiresharkMageia:5 |
before 2.0.11-1.mga5 | 2.0.11-1.mga5 |
wiresharkSUSE:Linux Enterprise Software Development Kit 11 SP4 From an advisory covering 23 CVEs |
before 2.0.12-36.1 | 2.0.12-36.1 |
wiresharkSUSE:Linux Enterprise Server 11 SP4 From an advisory covering 23 CVEs |
before 2.0.12-36.1 | 2.0.12-36.1 |
wiresharkSUSE:Linux Enterprise Server for SAP Applications 11 SP4 From an advisory covering 23 CVEs |
before 2.0.12-36.1 | 2.0.12-36.1 |
Show 11 moreShow less
| Package | Affected | Fixed |
|---|---|---|
wiresharkSUSE:Linux Enterprise Desktop 12 SP1 From an advisory covering 24 CVEs |
before 2.2.6-44.3 | 2.2.6-44.3 |
wiresharkSUSE:Linux Enterprise Desktop 12 SP2 From an advisory covering 24 CVEs |
before 2.2.6-44.3 | 2.2.6-44.3 |
wiresharkSUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 From an advisory covering 24 CVEs |
before 2.2.6-44.3 | 2.2.6-44.3 |
wiresharkSUSE:Linux Enterprise Software Development Kit 12 SP1 From an advisory covering 24 CVEs |
before 2.2.6-44.3 | 2.2.6-44.3 |
wiresharkSUSE:Linux Enterprise Software Development Kit 12 SP2 From an advisory covering 24 CVEs |
before 2.2.6-44.3 | 2.2.6-44.3 |
wiresharkSUSE:Linux Enterprise Server 12 SP1 From an advisory covering 24 CVEs |
before 2.2.6-44.3 | 2.2.6-44.3 |
wiresharkSUSE:Linux Enterprise Server for SAP Applications 12 SP1 From an advisory covering 24 CVEs |
before 2.2.6-44.3 | 2.2.6-44.3 |
wiresharkSUSE:Linux Enterprise Server 12 SP2 From an advisory covering 24 CVEs |
before 2.2.6-44.3 | 2.2.6-44.3 |
wiresharkSUSE:Linux Enterprise Server for SAP Applications 12 SP2 From an advisory covering 24 CVEs |
before 2.2.6-44.3 | 2.2.6-44.3 |
wiresharkUbuntu:14.04:LTS |
before 1.12.1+g01b65bf-4+deb8u11ubuntu0.14.04.1, plus listed versions 1.10.2-11.10.3-11.10.5-1ubuntu11.10.5-21.10.6-1 |
1.12.1+g01b65bf-4+deb8u11ubuntu0.14.04.1 |
wiresharkUbuntu:16.04:LTS |
before 2.2.6+g32dac6a-2ubuntu0.16.04, plus listed versions 1.12.7+g7fc8978-11.12.8+g5b6e543-22.0.1+g59ea380-3build12.0.2+ga16e22e-1 |
2.2.6+g32dac6a-2ubuntu0.16.04 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2017-6014 is a high vulnerability (CVSS 7.5) in Wireshark, published February 17, 2017. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 3.23%, the 88th percentile. Fixed in wireshark 2.2.4-r1.
References
securityfocus.com/bid/96284
security.gentoo.org/glsa/201706-12
debian.org/security/2017/dsa-3811
bugs.wireshark.org/bugzilla/show_bug.cgi?id=13416
nvd.nist.gov/vuln/detail/CVE-2017-6014
github.com/advisories/GHSA-8q6q-3849-7cm3
Show 71 moreShow less
security.alpinelinux.org/vuln/CVE-2017-6014
security-tracker.debian.org/tracker/CVE-2017-6014
advisories.mageia.org/MGASA-2017-0076.html
bugs.mageia.org/show_bug.cgi?id=20392
wireshark.org/security/wnpa-sec-2017-03.html
wireshark.org/security/wnpa-sec-2017-04.html
wireshark.org/security/wnpa-sec-2017-05.html
wireshark.org/security/wnpa-sec-2017-06.html
wireshark.org/security/wnpa-sec-2017-07.html
wireshark.org/security/wnpa-sec-2017-08.html
wireshark.org/security/wnpa-sec-2017-09.html
wireshark.org/security/wnpa-sec-2017-10.html
wireshark.org/security/wnpa-sec-2017-11.html
wireshark.org/docs/relnotes/wireshark-2.0.11.html
wireshark.org/news/20170303.html
suse.com/support/update/announcement/2017/suse-su-20171174-1
bugzilla.suse.com/1002981
bugzilla.suse.com/1010735
bugzilla.suse.com/1010740
bugzilla.suse.com/1010752
bugzilla.suse.com/1010754
bugzilla.suse.com/1010911
bugzilla.suse.com/1021739
bugzilla.suse.com/1025913
bugzilla.suse.com/1027998
bugzilla.suse.com/1033936
bugzilla.suse.com/1033937
bugzilla.suse.com/1033938
bugzilla.suse.com/1033939
bugzilla.suse.com/1033940
bugzilla.suse.com/1033941
bugzilla.suse.com/1033942
bugzilla.suse.com/1033943
bugzilla.suse.com/1033944
bugzilla.suse.com/1033945
bugzilla.suse.com/998761
bugzilla.suse.com/998762
bugzilla.suse.com/998763
bugzilla.suse.com/998800
bugzilla.suse.com/998963
bugzilla.suse.com/998964
suse.com/security/cve/CVE-2016-7175
suse.com/security/cve/CVE-2016-7176
suse.com/security/cve/CVE-2016-7177
suse.com/security/cve/CVE-2016-7178
suse.com/security/cve/CVE-2016-7179
suse.com/security/cve/CVE-2016-7180
suse.com/security/cve/CVE-2016-9373
suse.com/security/cve/CVE-2016-9374
suse.com/security/cve/CVE-2016-9375
suse.com/security/cve/CVE-2016-9376
suse.com/security/cve/CVE-2017-5596
suse.com/security/cve/CVE-2017-5597
suse.com/security/cve/CVE-2017-6014
suse.com/security/cve/CVE-2017-7700
suse.com/security/cve/CVE-2017-7701
suse.com/security/cve/CVE-2017-7702
suse.com/security/cve/CVE-2017-7703
suse.com/security/cve/CVE-2017-7704
suse.com/security/cve/CVE-2017-7705
suse.com/security/cve/CVE-2017-7745
suse.com/security/cve/CVE-2017-7746
suse.com/security/cve/CVE-2017-7747
suse.com/security/cve/CVE-2017-7748
suse.com/support/update/announcement/2017/suse-su-20171442-1
bugzilla.suse.com/1026507
bugzilla.suse.com/1027692
bugzilla.suse.com/990856
suse.com/security/cve/CVE-2016-6354
ubuntu.com/security/CVE-2017-6014
cve.org/CVERecord?id=CVE-2017-6014
Left out here: 13 versions and the rest of 2 source descriptions. The JSON record has them.