CVE-2017-7705
In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the RPC over RDMA dissector could go into an...
CVE-2017-7705 is a high vulnerability (CVSS 7.5) in Wireshark, published April 12, 2017. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 2.71%, the 85th percentile. Fixed in wireshark 2.2.6-r0.
In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, 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.
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.0 to 2.2.5 and 2.0.0 to 2.0.11, 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.
- Record
CVE-2017-7705- 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.0 to 2.2.5 and 2.0.0 to 2.0.11, 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.
- Record
CVE-2017-7705- Updated
- 2026-11-02
EUVDEUVD-2017-16681 No score
In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, 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.
- Record
EUVD-2017-16681- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-2wm6-mgmh-92vr
7.5
In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, the RPC over RDMA dissector could go into an...
In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, 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.
- Record
GHSA-2wm6-mgmh-92vr- 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-7705
7.5
In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, 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.
- Record
ALPINE-CVE-2017-7705- 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.0 to 2.2.5 and 2.0.0 to 2.0.11, 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.
- Record
CVE-2017-7705- 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 6 moreShow less
OSVDEBIAN-CVE-2017-7705
7.5
In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, 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.
- Record
DEBIAN-CVE-2017-7705- 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-7705
7.5
In Wireshark 2.2.0 to 2.2.5 and 2.0.0 to 2.0.11, 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.
- Record
UBUNTU-CVE-2017-7705- 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-0113 No score
Updated wireshark packages fix security vulnerability
The wireshark package has been updated to version 2.0.12, which fixes multiple 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-0113- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:11513-1 No score
libwireshark14-3.4.8-1.2 on GA media
These are all security issues fixed in the libwireshark14-3.4.8-1.2 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:11513-1- 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.6-r0 | 2.2.6-r0 |
wiresharkDebian:12 |
before 2.2.6+g32dac6a-1 | 2.2.6+g32dac6a-1 |
wiresharkDebian:13 |
before 2.2.6+g32dac6a-1 | 2.2.6+g32dac6a-1 |
wiresharkDebian:14 |
before 2.2.6+g32dac6a-1 | 2.2.6+g32dac6a-1 |
wiresharkMageia:5 |
before 2.0.12-1.mga5 | 2.0.12-1.mga5 |
wiresharkSUSE:Linux Enterprise Software Development Kit 11 SP4 |
before 2.0.12-36.1 | 2.0.12-36.1 |
wiresharkSUSE:Linux Enterprise Server 11 SP4 |
before 2.0.12-36.1 | 2.0.12-36.1 |
wiresharkSUSE:Linux Enterprise Server for SAP Applications 11 SP4 |
before 2.0.12-36.1 | 2.0.12-36.1 |
wiresharkSUSE:Linux Enterprise Desktop 12 SP1 |
before 2.2.6-44.3 | 2.2.6-44.3 |
wiresharkSUSE:Linux Enterprise Desktop 12 SP2 |
before 2.2.6-44.3 | 2.2.6-44.3 |
Show 11 moreShow less
| Package | Affected | Fixed |
|---|---|---|
wiresharkSUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 |
before 2.2.6-44.3 | 2.2.6-44.3 |
wiresharkSUSE:Linux Enterprise Software Development Kit 12 SP1 |
before 2.2.6-44.3 | 2.2.6-44.3 |
wiresharkSUSE:Linux Enterprise Software Development Kit 12 SP2 |
before 2.2.6-44.3 | 2.2.6-44.3 |
wiresharkSUSE:Linux Enterprise Server 12 SP1 |
before 2.2.6-44.3 | 2.2.6-44.3 |
wiresharkSUSE:Linux Enterprise Server for SAP Applications 12 SP1 |
before 2.2.6-44.3 | 2.2.6-44.3 |
wiresharkSUSE:Linux Enterprise Server 12 SP2 |
before 2.2.6-44.3 | 2.2.6-44.3 |
wiresharkSUSE:Linux Enterprise Server for SAP Applications 12 SP2 |
before 2.2.6-44.3 | 2.2.6-44.3 |
wiresharkUbuntu:14.04:LTS |
before 2.6.3-1~ubuntu14.04.1, plus listed versions 1.10.2-11.10.3-11.10.5-1ubuntu11.10.5-21.10.6-11.12.1+g01b65bf-4+deb8u11ubuntu0.14.04.1 |
2.6.3-1~ubuntu14.04.1 |
wiresharkUbuntu:16.04:LTS |
before 2.6.3-1~ubuntu16.04.1, plus listed versions 1.12.7+g7fc8978-11.12.8+g5b6e543-22.0.1+g59ea380-3build12.0.2+ga16e22e-12.2.6+g32dac6a-2ubuntu0.16.04 |
2.6.3-1~ubuntu16.04.1 |
wiresharkUbuntu:18.04:LTS |
before 2.6.3-1~ubuntu18.04.1, plus listed versions 2.4.2-12.4.3-12.4.4-12.4.5-1 |
2.6.3-1~ubuntu18.04.1 |
wiresharkopenSUSE:Tumbleweed |
before 3.4.8-1.2 | 3.4.8-1.2 |
History
| When | Changed | Sources |
|---|---|---|
| 2026-11-03 | aliases | EUVD |
| 2026-11-02 | created | CVE List, GitHub Advisories, NVD, OSV |
References
bugs.wireshark.org/bugzilla/show_bug.cgi?id=13558
code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=08d392bbecc8fb666bf979e70a34536007b83ea2
securityfocus.com/bid/97630
securitytracker.com/id/1038262
security.gentoo.org/glsa/201706-12
wireshark.org/security/wnpa-sec-2017-15.html
Show 194 moreShow less
nvd.nist.gov/vuln/detail/CVE-2017-7705
code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=08d392bbecc8fb666bf979e70a34536007b83ea2
github.com/advisories/GHSA-2wm6-mgmh-92vr
security.alpinelinux.org/vuln/CVE-2017-7705
security-tracker.debian.org/tracker/CVE-2017-7705
advisories.mageia.org/MGASA-2017-0113.html
bugs.mageia.org/show_bug.cgi?id=20673
wireshark.org/security/wnpa-sec-2017-04.html
wireshark.org/security/wnpa-sec-2017-12.html
wireshark.org/security/wnpa-sec-2017-13.html
wireshark.org/security/wnpa-sec-2017-14.html
wireshark.org/security/wnpa-sec-2017-16.html
wireshark.org/security/wnpa-sec-2017-18.html
wireshark.org/security/wnpa-sec-2017-19.html
wireshark.org/security/wnpa-sec-2017-20.html
wireshark.org/security/wnpa-sec-2017-21.html
wireshark.org/docs/relnotes/wireshark-2.0.12.html
wireshark.org/news/20170412.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-7705
cve.org/CVERecord?id=CVE-2017-7705
suse.com/security/cve/CVE-2006-1932
suse.com/security/cve/CVE-2006-4574
suse.com/security/cve/CVE-2006-4805
suse.com/security/cve/CVE-2006-5468
suse.com/security/cve/CVE-2006-5469
suse.com/security/cve/CVE-2006-5740
suse.com/security/cve/CVE-2007-0456
suse.com/security/cve/CVE-2007-0457
suse.com/security/cve/CVE-2007-0458
suse.com/security/cve/CVE-2007-0459
suse.com/security/cve/CVE-2017-11406
suse.com/security/cve/CVE-2017-11407
suse.com/security/cve/CVE-2017-11408
suse.com/security/cve/CVE-2017-13764
suse.com/security/cve/CVE-2017-13765
suse.com/security/cve/CVE-2017-13766
suse.com/security/cve/CVE-2017-13767
suse.com/security/cve/CVE-2017-15189
suse.com/security/cve/CVE-2017-15190
suse.com/security/cve/CVE-2017-15191
suse.com/security/cve/CVE-2017-15192
suse.com/security/cve/CVE-2017-15193
suse.com/security/cve/CVE-2017-17083
suse.com/security/cve/CVE-2017-17084
suse.com/security/cve/CVE-2017-17085
suse.com/security/cve/CVE-2017-5753
suse.com/security/cve/CVE-2017-6467
suse.com/security/cve/CVE-2017-6468
suse.com/security/cve/CVE-2017-6469
suse.com/security/cve/CVE-2017-6470
suse.com/security/cve/CVE-2017-6471
suse.com/security/cve/CVE-2017-6472
suse.com/security/cve/CVE-2017-6473
suse.com/security/cve/CVE-2017-6474
suse.com/security/cve/CVE-2017-9343
suse.com/security/cve/CVE-2017-9344
suse.com/security/cve/CVE-2017-9345
suse.com/security/cve/CVE-2017-9346
suse.com/security/cve/CVE-2017-9347
suse.com/security/cve/CVE-2017-9348
suse.com/security/cve/CVE-2017-9349
suse.com/security/cve/CVE-2017-9350
suse.com/security/cve/CVE-2017-9351
suse.com/security/cve/CVE-2017-9352
suse.com/security/cve/CVE-2017-9353
suse.com/security/cve/CVE-2017-9354
suse.com/security/cve/CVE-2018-11354
suse.com/security/cve/CVE-2018-11355
suse.com/security/cve/CVE-2018-11356
suse.com/security/cve/CVE-2018-11357
suse.com/security/cve/CVE-2018-11358
suse.com/security/cve/CVE-2018-11359
suse.com/security/cve/CVE-2018-11360
suse.com/security/cve/CVE-2018-11361
suse.com/security/cve/CVE-2018-11362
suse.com/security/cve/CVE-2018-12086
suse.com/security/cve/CVE-2018-14339
suse.com/security/cve/CVE-2018-14340
suse.com/security/cve/CVE-2018-14341
suse.com/security/cve/CVE-2018-14342
suse.com/security/cve/CVE-2018-14343
suse.com/security/cve/CVE-2018-14344
suse.com/security/cve/CVE-2018-14367
suse.com/security/cve/CVE-2018-14368
suse.com/security/cve/CVE-2018-14369
suse.com/security/cve/CVE-2018-14370
suse.com/security/cve/CVE-2018-16056
suse.com/security/cve/CVE-2018-16057
suse.com/security/cve/CVE-2018-16058
suse.com/security/cve/CVE-2018-18225
suse.com/security/cve/CVE-2018-18226
suse.com/security/cve/CVE-2018-18227
suse.com/security/cve/CVE-2018-19622
suse.com/security/cve/CVE-2018-19623
suse.com/security/cve/CVE-2018-19624
suse.com/security/cve/CVE-2018-19625
suse.com/security/cve/CVE-2018-19626
suse.com/security/cve/CVE-2018-19627
suse.com/security/cve/CVE-2018-19628
suse.com/security/cve/CVE-2018-5334
suse.com/security/cve/CVE-2018-5335
suse.com/security/cve/CVE-2018-5336
suse.com/security/cve/CVE-2018-7320
suse.com/security/cve/CVE-2018-7321
suse.com/security/cve/CVE-2018-7325
suse.com/security/cve/CVE-2018-7329
suse.com/security/cve/CVE-2018-7333
suse.com/security/cve/CVE-2018-7334
suse.com/security/cve/CVE-2018-7335
suse.com/security/cve/CVE-2018-7336
suse.com/security/cve/CVE-2018-7337
suse.com/security/cve/CVE-2018-7417
suse.com/security/cve/CVE-2018-7418
suse.com/security/cve/CVE-2018-7419
suse.com/security/cve/CVE-2018-7420
suse.com/security/cve/CVE-2018-9256
suse.com/security/cve/CVE-2018-9257
suse.com/security/cve/CVE-2018-9258
suse.com/security/cve/CVE-2018-9260
suse.com/security/cve/CVE-2018-9261
suse.com/security/cve/CVE-2018-9262
suse.com/security/cve/CVE-2018-9263
suse.com/security/cve/CVE-2018-9264
suse.com/security/cve/CVE-2018-9265
suse.com/security/cve/CVE-2018-9269
suse.com/security/cve/CVE-2018-9273
suse.com/security/cve/CVE-2019-10894
suse.com/security/cve/CVE-2019-10895
suse.com/security/cve/CVE-2019-10896
suse.com/security/cve/CVE-2019-10897
suse.com/security/cve/CVE-2019-10898
suse.com/security/cve/CVE-2019-10899
suse.com/security/cve/CVE-2019-10900
suse.com/security/cve/CVE-2019-10901
suse.com/security/cve/CVE-2019-10902
suse.com/security/cve/CVE-2019-10903
suse.com/security/cve/CVE-2019-13619
suse.com/security/cve/CVE-2019-16319
suse.com/security/cve/CVE-2019-19553
suse.com/security/cve/CVE-2019-5716
Left out here: 31 references and the rest of 2 source descriptions. The JSON record has them.