CVE-2015-8743 json
QEMU (aka Quick Emulator) built with the NE2000 device emulation support is vulnerable to an OOB r/w access issue.
published 9y ago modified 4mo ago also EUVD-2015-8620
- cvss
- 7.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 38%
- public exploits
- 0
- none known
Summary
QEMU (aka Quick Emulator) built with the NE2000 device emulation support is vulnerable to an OOB r/w access issue. It could occur while performing 'ioport' r/w operations. A privileged (CAP_SYS_RAWIO) user/process could use this flaw to leak or corrupt QEMU memory bytes.
Patch / fix
- qemu Debian 14, Debian 13, Debian 12 1:2.5+dfsg-2
debian advisories DEBIAN-CVE-2015-8743
- qemu Ubuntu 14.04 LTS 2.0.0+dfsg-2ubuntu1.22
ubuntu advisories UBUNTU-CVE-2015-8743
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kvm SLES for SAP 11 SP4, SLES 11 SP4 1.4.2-44.1
- qemu SLES for SAP 12 SP1, SLES 12 SP1, SLED 12 SP1 2.3.1-14.1
- kvm SLES 11 SP3-TERADATA, SLES 11 SP3-LTSS 1.4.2-46.1
- qemu SLES for SAP 12, SLES 12, SLED 12 2.0.2-48.19.1
- xen SLES for SAP 12, SLES 12, SLED 12 +1 more 4.4.4_02-22.19.1
- xen SLES for SAP 11 SP4, SLES 11 SP4, SLED 11 SP4 +1 more 4.4.4_02-32.1
- xen SLES for SAP 12 SP1, SLES 12 SP1, SLED 12 SP1 +1 more 4.5.2_06-7.1
- xen SLES 11 SP3-LTSS 4.2.5_20-24.9
suse advisories SUSE-SU-2016:1785-1SUSE-SU-2016:1745-1SUSE-SU-2016:1703-1SUSE-SU-2016:1698-1SUSE-SU-2016:1560-1SUSE-SU-2016:1318-1
- xen openSUSE Tumbleweed 4.7.0_12-1.3
opensuse advisories openSUSE-SU-2024:10196-1
Is CVE-2015-8743 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2015-8743 updated cvss 3.8
Qemu: net: ne2000: OOB memory access in ioport r/w functions
-
Red Hat Enterprise Linux 5 kvm, xen Red Hat Enterprise Linux 6 qemu-img, qemu-kvm, qemu-kvm-tools, qemu-guest-agent, qemu-guest-agent-win32 Red Hat Enterprise Linux OpenStack Platform 5 (Icehouse) qemu-kvm-rhevaffected: no fix planned “Will not fix”
-
Red Hat Enterprise Linux 7 qemu-img, qemu-kvm, libcacard, qemu-kvm-rhev, qemu-kvm-tools, libcacard-tools, +2 more Red Hat Enterprise Linux OpenStack Platform 6 (Juno) qemu-kvm-rhev Red Hat Enterprise Linux OpenStack Platform 7 (Kilo) qemu-img-rhev, qemu-kvm-rhev, libcacard-rhev, qemu-kvm-tools-rhev, libcacard-devel-rhev, libcacard-tools-rhev, +1 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.45% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
| NVD | 2.0 | 3.6 | AV:L/AC:L/Au:N/C:P/I:P/A:N |
Classification
References
-
lists.gnu.org
/archive/html/qemu-devel/2016-01/msg00050.html
mailing-list, patch, vendor-advisory
-
debian.org
/security/2016/dsa-3469
vendor-advisory, third-party-advisory
-
debian.org
/security/2016/dsa-3470
vendor-advisory, third-party-advisory
-
debian.org
/security/2016/dsa-3471
vendor-advisory, third-party-advisory
-
security.gentoo.org
/glsa/201602-01
vendor-advisory, third-party-advisory
-
openwall.com
/lists/oss-security/2016/01/04/2
mailing-list, third-party-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=1264929
issue-tracking
-
securitytracker.com
/id/1034574
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/79820
vdb-entry, third-party-advisory
-
openwall.com
/lists/oss-security/2016/01/04/1
mailing-list, third-party-advisory
Sources
- CVE List CVE-2015-8743
- NVD CVE-2015-8743
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.