CVE-2017-8380
Buffer overflow in the "megasas_mmio_write" function in Qemu 2.9.0 allows remote attackers to...
Buffer overflow in the "megasas_mmio_write" function in Qemu 2.9.0 allows remote attackers to have unspecified impact via unknown vectors.
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
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
9.8
Buffer overflow in the "megasas_mmio_write" function in Qemu 2.9.0 allows remote attackers to have unspecified impact via unknown vectors.
- Record
CVE-2017-8380- CVSS 3.0
- 9.8 Critical
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - CVSS 2.0
- 7.5 High
AV:N/AC:L/Au:N/C:P/I:P/A:P - Weakness
- CWE-119
- Updated
- 2026-11-02
CVE List No score
Buffer overflow in the "megasas_mmio_write" function in Qemu 2.9.0 allows remote attackers to have unspecified impact via unknown vectors.
- Record
CVE-2017-8380- Updated
- 2026-11-02
EUVDEUVD-2017-17337 No score
Buffer overflow in the "megasas_mmio_write" function in Qemu 2.9.0 allows remote attackers to have unspecified impact via unknown vectors.
- Record
EUVD-2017-17337- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-4xjw-56mf-3pfv
9.8
Buffer overflow in the "megasas_mmio_write" function in Qemu 2.9.0 allows remote attackers to...
Buffer overflow in the "megasas_mmio_write" function in Qemu 2.9.0 allows remote attackers to have unspecified impact via unknown vectors.
- Record
GHSA-4xjw-56mf-3pfv- CVSS 3.0
- 9.8 Critical
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-119
- Updated
- 2026-11-02
OSV
9.8
Buffer overflow in the "megasas_mmio_write" function in Qemu 2.9.0 allows remote attackers to have unspecified impact via unknown vectors.
- Record
CVE-2017-8380- CVSS 3.0
- 9.8 Critical
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVDEBIAN-CVE-2017-8380
9.8
Buffer overflow in the "megasas_mmio_write" function in Qemu 2.9.0 allows remote attackers to have unspecified impact via unknown vectors.
- Record
DEBIAN-CVE-2017-8380- CVSS 3.0
- 9.8 Critical
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
Show 5 moreShow less
OSVUBUNTU-CVE-2017-8380
9.8
Buffer overflow in the "megasas_mmio_write" function in Qemu 2.9.0 allows remote attackers to have unspecified impact via unknown vectors.
- Record
UBUNTU-CVE-2017-8380- CVSS 3.0
- 9.8 Critical
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVopenSUSE-SU-2024:11287-1 No score
qemu-6.1.0-32.1 on GA media
These are all security issues fixed in the qemu-6.1.0-32.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:11287-1- Updated
- 2026-11-02
OSVSUSE-SU-2017:1774-1 No score
Security update for qemu
This update for qemu fixes several issues.
These security issues were fixed:
- CVE-2017-9330: USB OHCI Emulation in qemu allowed local guest OS users to cause a denial of service (infinite loop) by leveraging an incorrect return value (bsc#1042159).
- CVE-2017-8379: Memory leak in the keyboard input event handlers support allowed local guest OS privileged users to cause a denial of service (host memory consumption) by rapidly generating large keyboard events (bsc#1037334).
- CVE-2017-8309: Memory leak in the audio/audio.c allowed remote attackers to cause a denial of service (memory consumption) by repeatedly starting and stopping audio capture (bsc#1037242).
- CVE-2017-7493: The VirtFS, host directory sharing via Plan 9 File System(9pfs) support, was vulnerable to an improper access control issue. It could occur while accessing virtfs metadata files in mapped-file security mode. A guest user could have used this flaw to escalate their privileges inside guest (bsc#1039495).
- CVE-2017-7377: The v9fs_create and v9fs_lcreate functions in hw/9pfs/9p.c allowed local guest OS privileged users to cause a denial of service (file descriptor or memory consumption) via vectors related to an already in-use fid (bsc#1032075).
- CVE-2017-8086: A memory leak in the v9fs_list_xattr function in hw/9pfs/9p-xattr.c allowed local guest OS privileged users to cause a denial of service (memory consumption) via vectors involving the orig_value variable (bsc#1035950).
- CVE-2017-5973: A infinite loop while doing control transfer in xhci_kick_epctx allowed privileged user inside the guest to crash the host process resulting in DoS (bsc#1025109)
- CVE-2017-5987: The sdhci_sdma_transfer_multi_blocks function in hw/sd/sdhci.c allowed local OS guest privileged users to cause a denial of service (infinite loop and QEMU process crash) via vectors involving the transfer mode register during multi block transfer (bsc#1025311).
- CVE-2017-6505: The ohci_service_ed_list function in hw/usb/hcd-ohci.c allowed local guest OS users to cause a denial of service (infinite loop) via vectors involving the number of link endpoint list descriptors (bsc#1028184)
- CVE-2016-9603: A privileged user within the guest VM could have caused a heap overflow in the device model process, potentially escalating their privileges to that of the device model process (bsc#1028656)
- CVE-2017-7718: hw/display/cirrus_vga_rop.h allowed local guest OS privileged users to cause a denial of service (out-of-bounds read and QEMU process crash) via vectors related to copying VGA data via the cirrus_bitblt_rop_fwd_transp_ and cirrus_bitblt_rop_fwd_ functions (bsc#1034908)
- CVE-2017-7980: An out-of-bounds r/w access issues in the Cirrus CLGD 54xx VGA Emulator support allowed privileged user inside guest to use this flaw to crash the Qemu process resulting in DoS or potentially execute arbitrary code on a host with privileges of Qemu process on the host (bsc#1035406)
- CVE-2017-8112: hw/scsi/vmw_pvscsi.c allowed local guest OS privileged users to cause a denial of service (infinite loop and CPU consumption) via the message ring page count (bsc#1036211).
- CVE-2017-9375: The USB xHCI controller emulator support was vulnerable to an infinite recursive call loop issue, which allowed a privileged user inside guest to crash the Qemu process resulting in DoS (bsc#1042800).
- CVE-2017-9374: Missing free of 's->ipacket', causes a host memory leak, allowing for DoS (bsc#1043073).
- CVE-2017-9373: The IDE AHCI Emulation support was vulnerable to a host memory leakage issue, which allowed a privileged user inside guest to leak host memory resulting in DoS (bsc#1042801).
- CVE-2017-8380: The MegaRAID SAS 8708EM2 Host Bus Adapter emulation support was vulnerable to an out-of-bounds read access issue which allowed a privileged user inside guest to read host memory resulting in DoS (bsc#1037336).
- CVE-2016-9602: The VirtFS host directory sharing via Plan 9 File System(9pfs) support was vulnerable to an…
- Record
SUSE-SU-2017:1774-1- Updated
- 2026-11-02
OSVSUSE-SU-2017:2946-1 No score
Security update for qemu
This update for qemu fixes several issues.
These security issues were fixed:
- CVE-2017-10911: The make_response function in the Linux kernel allowed guest OS users to obtain sensitive information from host OS (or other guest OS) kernel memory by leveraging the copying of uninitialized padding fields in Xen block-interface response structures (bsc#1057378).
- CVE-2017-12809: The IDE disk and CD/DVD-ROM Emulator support allowed local guest OS privileged users to cause a denial of service (NULL pointer dereference and QEMU process crash) by flushing an empty CDROM device drive (bsc#1054724).
- CVE-2017-15289: The mode4and5 write functions allowed local OS guest privileged users to cause a denial of service (out-of-bounds write access and Qemu process crash) via vectors related to dst calculation (bsc#1063122)
- CVE-2017-15038: Race condition in the v9fs_xattrwalk function local guest OS users to obtain sensitive information from host heap memory via vectors related to reading extended attributes (bsc#1062069)
- CVE-2017-14167: Integer overflow in the load_multiboot function allowed local guest OS users to execute arbitrary code on the host via crafted multiboot header address values, which trigger an out-of-bounds write (bsc#1057585)
- CVE-2017-11434: The dhcp_decode function in slirp/bootp.c allowed local guest OS users to cause a denial of service (out-of-bounds read) via a crafted DHCP options string (bsc#1049381)
- CVE-2017-11334: The address_space_write_continue function allowed local guest OS privileged users to cause a denial of service (out-of-bounds access and guest instance crash) by leveraging use of qemu_map_ram_ptr to access guest ram block area (bsc#1048902)
- CVE-2017-13672: The VGA display emulator support allowed local guest OS privileged users to cause a denial of service (out-of-bounds read and QEMU process crash) via vectors involving display update (bsc#1056334)
- CVE-2017-5973: A infinite loop while doing control transfer in xhci_kick_epctx allowed privileged user inside the guest to crash the host process resulting in DoS (bsc#1025109)
- CVE-2017-5987: The sdhci_sdma_transfer_multi_blocks function in hw/sd/sdhci.c allowed local OS guest privileged users to cause a denial of service (infinite loop and QEMU process crash) via vectors involving the transfer mode register during multi block transfer (bsc#1025311)
- CVE-2017-6505: The ohci_service_ed_list function allowed local guest OS users to cause a denial of service (infinite loop) via vectors involving the number of link endpoint list descriptors (bsc#1028184)
- CVE-2016-9603: A privileged user within the guest VM could have caused a heap overflow in the device model process, potentially escalating their privileges to that of the device model process (bsc#1028656)
- CVE-2017-7718: hw/display/cirrus_vga_rop.h allowed local guest OS privileged users to cause a denial of service (out-of-bounds read and QEMU process crash) via vectors related to copying VGA data via the cirrus_bitblt_rop_fwd_transp_ and cirrus_bitblt_rop_fwd_ functions (bsc#1034908)
- CVE-2017-7980: An out-of-bounds r/w access issues in the Cirrus CLGD 54xx VGA Emulator support allowed privileged user inside guest to use this flaw to crash the Qemu process resulting in DoS or potentially execute arbitrary code on a host with privileges of Qemu process on the host (bsc#1035406)
- CVE-2017-8112: hw/scsi/vmw_pvscsi.c allowed local guest OS privileged users to cause a denial of service (infinite loop and CPU consumption) via the message ring page count (bsc#1036211)
- CVE-2017-9375: The USB xHCI controller emulator support was vulnerable to an infinite recursive call loop issue, which allowed a privileged user inside guest to crash the Qemu process resulting in DoS (bsc#1042800)
- CVE-2017-9374: Missing free of 's->ipacket', causes a host memory leak, allowing for DoS (bsc#1043073)
- CVE-2017-9373: The IDE AHCI Emulation support was vulnerable to a host memory leakage issue, which allowed a…
- Record
SUSE-SU-2017:2946-1- Updated
- 2026-11-02
OSVUSN-3414-1 No score
qemu vulnerabilities
Leo Gaspard discovered that QEMU incorrectly handled VirtFS access control. A guest attacker could use this issue to elevate privileges inside the guest. (CVE-2017-7493)
Li Qiang discovered that QEMU incorrectly handled VMWare PVSCSI emulation. A privileged attacker inside the guest could use this issue to cause QEMU to consume resources or crash, resulting in a denial of service. (CVE-2017-8112)
It was discovered that QEMU incorrectly handled MegaRAID SAS 8708EM2 Host Bus Adapter emulation support. A privileged attacker inside the guest could use this issue to cause QEMU to crash, resulting in a denial of service, or possibly to obtain sensitive host memory. This issue only affected Ubuntu 16.04 LTS and Ubuntu 17.04. (CVE-2017-8380)
Li Qiang discovered that QEMU incorrectly handled the Virtio GPU device. An attacker inside the guest could use this issue to cause QEMU to consume resources and crash, resulting in a denial of service. This issue only affected Ubuntu 17.04. (CVE-2017-9060)
Li Qiang discovered that QEMU incorrectly handled the e1000e device. A privileged attacker inside the guest could use this issue to cause QEMU to hang, resulting in a denial of service. This issue only affected Ubuntu 17.04. (CVE-2017-9310)
Li Qiang discovered that QEMU incorrectly handled USB OHCI emulation support. An attacker inside the guest could use this issue to cause QEMU to crash, resulting in a denial of service. (CVE-2017-9330)
Li Qiang discovered that QEMU incorrectly handled IDE AHCI emulation support. A privileged attacker inside the guest could use this issue to cause QEMU to consume resources and crash, resulting in a denial of service. (CVE-2017-9373)
Li Qiang discovered that QEMU incorrectly handled USB EHCI emulation support. A privileged attacker inside the guest could use this issue to cause QEMU to consume resources and crash, resulting in a denial of service. (CVE-2017-9374)
Li Qiang discovered that QEMU incorrectly handled USB xHCI emulation support. A privileged attacker inside the guest could use this issue to cause QEMU to hang, resulting in a denial of service. (CVE-2017-9375)
Zhangyanyu discovered that QEMU incorrectly handled MegaRAID SAS 8708EM2 Host Bus Adapter emulation support. A privileged attacker inside the guest could use this issue to cause QEMU to crash, resulting in a denial of service. (CVE-2017-9503)
It was discovered that the QEMU qemu-nbd server incorrectly handled initialization. A remote attacker could use this issue to cause the server to crash, resulting in a denial of service. (CVE-2017-9524)
It was discovered that the QEMU qemu-nbd server incorrectly handled signals. A remote attacker could use this issue to cause the server to crash, resulting in a denial of service. (CVE-2017-10664)
Li Qiang discovered that the QEMU USB redirector incorrectly handled logging debug messages. An attacker inside the guest could use this issue to cause QEMU to crash, resulting in a denial of service. (CVE-2017-10806)
Anthony Perard discovered that QEMU incorrectly handled Xen block-interface responses. An attacker inside the guest could use this issue to cause QEMU to leak contents of host memory. (CVE-2017-10911)
Reno Robert discovered that QEMU incorrectly handled certain DHCP options strings. An attacker inside the guest could use this issue to cause QEMU to crash, resulting in a denial of service. (CVE-2017-11434)
Ryan Salsamendi discovered that QEMU incorrectly handled empty CDROM device drives. A privileged attacker inside the guest could use this issue to cause QEMU to crash, resulting in a denial of service. This issue only affected Ubuntu 16.04 LTS and Ubuntu 17.04. (CVE-2017-12809)
- Record
USN-3414-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
qemuDebian:12 |
before 1:2.8+dfsg-5 | 1:2.8+dfsg-5 |
qemuDebian:13 |
before 1:2.8+dfsg-5 | 1:2.8+dfsg-5 |
qemuDebian:14 |
before 1:2.8+dfsg-5 | 1:2.8+dfsg-5 |
qemuSUSE:Linux Enterprise Desktop 12 SP2 |
before 2.6.2-41.16.1 | 2.6.2-41.16.1 |
qemuSUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 |
before 2.6.2-41.16.1 | 2.6.2-41.16.1 |
qemuSUSE:Linux Enterprise Server 12 SP2 |
before 2.6.2-41.16.1 | 2.6.2-41.16.1 |
qemuSUSE:Linux Enterprise Server for SAP Applications 12 SP2 |
before 2.6.2-41.16.1 | 2.6.2-41.16.1 |
qemuSUSE:OpenStack Cloud 6 |
before 2.3.1-33.3.3 | 2.3.1-33.3.3 |
qemuSUSE:Linux Enterprise Server for SAP Applications 12 SP1 |
before 2.3.1-33.3.3 | 2.3.1-33.3.3 |
qemuSUSE:Linux Enterprise Server 12 SP1-LTSS |
before 2.3.1-33.3.3 | 2.3.1-33.3.3 |
qemuUbuntu:16.04:LTS |
before 1:2.5+dfsg-5ubuntu10.15, plus listed versions 1:2.3+dfsg-5ubuntu91:2.3+dfsg-5ubuntu101:2.4+dfsg-4ubuntu11:2.4+dfsg-4ubuntu21:2.4+dfsg-4ubuntu3 Show 24 moreShow less1:2.4+dfsg-5ubuntu31:2.5+dfsg-1ubuntu21:2.5+dfsg-1ubuntu31:2.5+dfsg-1ubuntu41:2.5+dfsg-1ubuntu51:2.5+dfsg-5ubuntu11:2.5+dfsg-5ubuntu21:2.5+dfsg-5ubuntu41:2.5+dfsg-5ubuntu61:2.5+dfsg-5ubuntu71:2.5+dfsg-5ubuntu101:2.5+dfsg-5ubuntu10.11:2.5+dfsg-5ubuntu10.21:2.5+dfsg-5ubuntu10.31:2.5+dfsg-5ubuntu10.41:2.5+dfsg-5ubuntu10.51:2.5+dfsg-5ubuntu10.61:2.5+dfsg-5ubuntu10.71:2.5+dfsg-5ubuntu10.81:2.5+dfsg-5ubuntu10.91:2.5+dfsg-5ubuntu10.101:2.5+dfsg-5ubuntu10.111:2.5+dfsg-5ubuntu10.131:2.5+dfsg-5ubuntu10.14 |
1:2.5+dfsg-5ubuntu10.15 |
qemuUbuntu:14.04:LTS |
before 2.0.0+dfsg-2ubuntu1.35, plus listed versions 1.5.0+dfsg-3ubuntu51.5.0+dfsg-3ubuntu61.6.0+dfsg-2ubuntu11.6.0+dfsg-2ubuntu21.6.0+dfsg-2ubuntu3 Show 45 moreShow less1.6.0+dfsg-2ubuntu41.7.0+dfsg-2ubuntu11.7.0+dfsg-2ubuntu21.7.0+dfsg-2ubuntu31.7.0+dfsg-2ubuntu41.7.0+dfsg-2ubuntu51.7.0+dfsg-2ubuntu71.7.0+dfsg-2ubuntu81.7.0+dfsg-2ubuntu91.7.0+dfsg-3ubuntu1~ppa11.7.0+dfsg-3ubuntu11.7.0+dfsg-3ubuntu21.7.0+dfsg-3ubuntu31.7.0+dfsg-3ubuntu41.7.0+dfsg-3ubuntu51.7.0+dfsg-3ubuntu61.7.0+dfsg-3ubuntu72.0.0~rc1+dfsg-0ubuntu12.0.0~rc1+dfsg-0ubuntu22.0.0~rc1+dfsg-0ubuntu32.0.0~rc1+dfsg-0ubuntu3.12.0.0+dfsg-2ubuntu12.0.0+dfsg-2ubuntu1.12.0.0+dfsg-2ubuntu1.22.0.0+dfsg-2ubuntu1.32.0.0+dfsg-2ubuntu1.52.0.0+dfsg-2ubuntu1.62.0.0+dfsg-2ubuntu1.72.0.0+dfsg-2ubuntu1.82.0.0+dfsg-2ubuntu1.92.0.0+dfsg-2ubuntu1.102.0.0+dfsg-2ubuntu1.112.0.0+dfsg-2ubuntu1.132.0.0+dfsg-2ubuntu1.142.0.0+dfsg-2ubuntu1.152.0.0+dfsg-2ubuntu1.162.0.0+dfsg-2ubuntu1.172.0.0+dfsg-2ubuntu1.182.0.0+dfsg-2ubuntu1.192.0.0+dfsg-2ubuntu1.202.0.0+dfsg-2ubuntu1.212.0.0+dfsg-2ubuntu1.222.0.0+dfsg-2ubuntu1.242.0.0+dfsg-2ubuntu1.252.0.0+dfsg-2ubuntu1.26 |
2.0.0+dfsg-2ubuntu1.35 |
qemuopenSUSE:Tumbleweed |
before 6.1.0-32.1 | 6.1.0-32.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| 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-8380 is a critical vulnerability (CVSS 9.8) in Qemu, published July 4, 2017. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 3.91%, the 90th percentile. Fixed in qemu 1:2.8+dfsg-5.
References
security.gentoo.org/glsa/201706-03
lists.gnu.org/archive/html/qemu-devel/2017-04/msg04147.html
securityfocus.com/bid/98303
nvd.nist.gov/vuln/detail/CVE-2017-8380
github.com/advisories/GHSA-4xjw-56mf-3pfv
security-tracker.debian.org/tracker/CVE-2017-8380
Show 194 moreShow less
suse.com/support/update/announcement/2017/suse-su-20171774-1
bugzilla.suse.com/1016503
bugzilla.suse.com/1016504
bugzilla.suse.com/1017081
bugzilla.suse.com/1017084
bugzilla.suse.com/1020427
bugzilla.suse.com/1021741
bugzilla.suse.com/1025109
bugzilla.suse.com/1025311
bugzilla.suse.com/1028184
bugzilla.suse.com/1028656
bugzilla.suse.com/1030624
bugzilla.suse.com/1031142
bugzilla.suse.com/1032075
bugzilla.suse.com/1034866
bugzilla.suse.com/1034908
bugzilla.suse.com/1035406
bugzilla.suse.com/1035950
bugzilla.suse.com/1036211
bugzilla.suse.com/1037242
bugzilla.suse.com/1037334
bugzilla.suse.com/1037336
bugzilla.suse.com/1039495
bugzilla.suse.com/1042159
bugzilla.suse.com/1042800
bugzilla.suse.com/1042801
bugzilla.suse.com/1043073
bugzilla.suse.com/1043296
suse.com/security/cve/CVE-2016-10028
suse.com/security/cve/CVE-2016-10029
suse.com/security/cve/CVE-2016-9602
suse.com/security/cve/CVE-2016-9603
suse.com/security/cve/CVE-2017-5579
suse.com/security/cve/CVE-2017-5973
suse.com/security/cve/CVE-2017-5987
suse.com/security/cve/CVE-2017-6505
suse.com/security/cve/CVE-2017-7377
suse.com/security/cve/CVE-2017-7471
suse.com/security/cve/CVE-2017-7493
suse.com/security/cve/CVE-2017-7718
suse.com/security/cve/CVE-2017-7980
suse.com/security/cve/CVE-2017-8086
suse.com/security/cve/CVE-2017-8112
suse.com/security/cve/CVE-2017-8309
suse.com/security/cve/CVE-2017-8379
suse.com/security/cve/CVE-2017-8380
suse.com/security/cve/CVE-2017-9330
suse.com/security/cve/CVE-2017-9373
suse.com/security/cve/CVE-2017-9374
suse.com/security/cve/CVE-2017-9375
suse.com/security/cve/CVE-2017-9503
suse.com/support/update/announcement/2017/suse-su-20172946-1
bugzilla.suse.com/1045035
bugzilla.suse.com/1046636
bugzilla.suse.com/1047674
bugzilla.suse.com/1048902
bugzilla.suse.com/1049381
bugzilla.suse.com/1054724
bugzilla.suse.com/1056334
bugzilla.suse.com/1057378
bugzilla.suse.com/1057585
bugzilla.suse.com/1062069
bugzilla.suse.com/1063122
bugzilla.suse.com/994418
bugzilla.suse.com/994605
suse.com/security/cve/CVE-2016-6834
suse.com/security/cve/CVE-2016-6835
suse.com/security/cve/CVE-2017-10664
suse.com/security/cve/CVE-2017-10806
suse.com/security/cve/CVE-2017-10911
suse.com/security/cve/CVE-2017-11334
suse.com/security/cve/CVE-2017-11434
suse.com/security/cve/CVE-2017-12809
suse.com/security/cve/CVE-2017-13672
suse.com/security/cve/CVE-2017-14167
suse.com/security/cve/CVE-2017-15038
suse.com/security/cve/CVE-2017-15289
ubuntu.com/security/CVE-2017-8380
ubuntu.com/security/notices/USN-3414-1
cve.org/CVERecord?id=CVE-2017-8380
ubuntu.com/security/CVE-2017-7493
ubuntu.com/security/CVE-2017-8112
ubuntu.com/security/CVE-2017-9060
ubuntu.com/security/CVE-2017-9310
ubuntu.com/security/CVE-2017-9330
ubuntu.com/security/CVE-2017-9373
ubuntu.com/security/CVE-2017-9374
ubuntu.com/security/CVE-2017-9375
ubuntu.com/security/CVE-2017-9503
ubuntu.com/security/CVE-2017-9524
ubuntu.com/security/CVE-2017-10664
ubuntu.com/security/CVE-2017-10806
ubuntu.com/security/CVE-2017-10911
ubuntu.com/security/CVE-2017-11434
ubuntu.com/security/CVE-2017-12809
suse.com/security/cve/CVE-2014-0222
suse.com/security/cve/CVE-2014-8106
suse.com/security/cve/CVE-2015-5225
suse.com/security/cve/CVE-2015-6855
suse.com/security/cve/CVE-2015-8504
suse.com/security/cve/CVE-2015-8619
suse.com/security/cve/CVE-2016-10155
suse.com/security/cve/CVE-2016-1714
suse.com/security/cve/CVE-2016-6490
suse.com/security/cve/CVE-2016-6836
suse.com/security/cve/CVE-2016-7156
suse.com/security/cve/CVE-2016-7157
suse.com/security/cve/CVE-2016-7161
suse.com/security/cve/CVE-2016-7170
suse.com/security/cve/CVE-2016-7421
suse.com/security/cve/CVE-2016-7422
suse.com/security/cve/CVE-2016-7423
suse.com/security/cve/CVE-2016-7466
suse.com/security/cve/CVE-2016-7907
suse.com/security/cve/CVE-2016-7908
suse.com/security/cve/CVE-2016-7909
suse.com/security/cve/CVE-2016-7994
suse.com/security/cve/CVE-2016-7995
suse.com/security/cve/CVE-2016-8576
suse.com/security/cve/CVE-2016-8577
suse.com/security/cve/CVE-2016-8578
suse.com/security/cve/CVE-2016-8667
suse.com/security/cve/CVE-2016-8668
suse.com/security/cve/CVE-2016-8669
suse.com/security/cve/CVE-2016-8909
suse.com/security/cve/CVE-2016-8910
suse.com/security/cve/CVE-2016-9101
suse.com/security/cve/CVE-2016-9102
suse.com/security/cve/CVE-2016-9103
suse.com/security/cve/CVE-2016-9104
suse.com/security/cve/CVE-2016-9105
suse.com/security/cve/CVE-2016-9106
suse.com/security/cve/CVE-2016-9907
suse.com/security/cve/CVE-2016-9921
suse.com/security/cve/CVE-2017-13673
suse.com/security/cve/CVE-2017-13711
suse.com/security/cve/CVE-2017-15118
suse.com/security/cve/CVE-2017-15268
suse.com/security/cve/CVE-2017-2615
suse.com/security/cve/CVE-2017-2620
suse.com/security/cve/CVE-2017-2630
suse.com/security/cve/CVE-2017-5525
suse.com/security/cve/CVE-2017-5526
suse.com/security/cve/CVE-2017-5552
suse.com/security/cve/CVE-2017-5578
suse.com/security/cve/CVE-2017-5667
suse.com/security/cve/CVE-2017-5715
suse.com/security/cve/CVE-2017-5856
suse.com/security/cve/CVE-2017-5857
suse.com/security/cve/CVE-2017-5898
suse.com/security/cve/CVE-2017-6058
suse.com/security/cve/CVE-2017-9524
suse.com/security/cve/CVE-2018-10839
suse.com/security/cve/CVE-2018-11806
suse.com/security/cve/CVE-2018-12126
suse.com/security/cve/CVE-2018-12130
suse.com/security/cve/CVE-2018-12207
suse.com/security/cve/CVE-2018-15746
suse.com/security/cve/CVE-2018-16872
suse.com/security/cve/CVE-2018-17963
suse.com/security/cve/CVE-2018-20123
suse.com/security/cve/CVE-2018-20124
suse.com/security/cve/CVE-2018-20125
suse.com/security/cve/CVE-2018-20126
suse.com/security/cve/CVE-2018-20191
suse.com/security/cve/CVE-2018-20216
suse.com/security/cve/CVE-2018-20815
suse.com/security/cve/CVE-2018-3639
suse.com/security/cve/CVE-2018-7858
suse.com/security/cve/CVE-2019-03812
suse.com/security/cve/CVE-2019-11135
suse.com/security/cve/CVE-2019-12155
suse.com/security/cve/CVE-2019-13164
suse.com/security/cve/CVE-2019-14378
suse.com/security/cve/CVE-2019-15890
suse.com/security/cve/CVE-2019-6778
suse.com/security/cve/CVE-2019-8934
suse.com/security/cve/CVE-2019-9824
suse.com/security/cve/CVE-2020-10702
suse.com/security/cve/CVE-2020-10717
suse.com/security/cve/CVE-2020-10761
suse.com/security/cve/CVE-2020-11102
suse.com/security/cve/CVE-2020-11869
suse.com/security/cve/CVE-2020-13361
suse.com/security/cve/CVE-2020-13362
suse.com/security/cve/CVE-2020-13659
suse.com/security/cve/CVE-2020-13800
suse.com/security/cve/CVE-2020-14364
suse.com/security/cve/CVE-2020-16092
suse.com/security/cve/CVE-2020-1711
suse.com/security/cve/CVE-2020-17380
suse.com/security/cve/CVE-2020-1983
suse.com/security/cve/CVE-2020-25085
suse.com/security/cve/CVE-2020-25723
Left out here: 8 versions, 18 references and the rest of 2 source descriptions. The JSON record has them.