CVE-2016-4020
What it is
The patch_instruction function in hw/i386/kvmvapic.c in QEMU does not initialize the imm32 variable, which allows local guest OS administrators to obtain sensitive information from host stack memory by accessing the Task Priority Register (TPR).
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure.
- Exploit odds
- 0.4% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.4% in the next 30 days (EPSS).
- Severity: 6.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.4% · EPSS, next 30 days
- Record status
- Modified
Affected
- Qemu ≤ 2.6.2
- Canonical Ubuntu Linux 12.04
- Canonical Ubuntu Linux 14.04
- Canonical Ubuntu Linux 15.10
- Canonical Ubuntu Linux 16.04
- Debian Linux 8.0
- Redhat Openstack 6.0
- Redhat Openstack 7.0
Attack profile CVSS 3.1 · 6.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2016-4020.md and follow it. Check whether this project is affected by CVE-2016-4020. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://lists.gnu.org/archive/html/qemu-devel/2016-04/msg01106.html
- https://lists.gnu.org/archive/html/qemu-devel/2016-04/msg01118.html
- https://lists.gnu.org/archive/html/qemu-devel/2016-04/msg01106.html
- https://lists.gnu.org/archive/html/qemu-devel/2016-04/msg01118.html
References
- http://git.qemu.org/?p=qemu.git%3Ba=commit%3Bh=691a02e2ce0c413236a78dee6f2651c937b09fb0
- http://www.securityfocus.com/bid/86067
- http://www.ubuntu.com/usn/USN-2974-1
- https://access.redhat.com/errata/RHSA-2017:1856
- https://access.redhat.com/errata/RHSA-2017:2392
- https://access.redhat.com/errata/RHSA-2017:2408
- https://bugzilla.redhat.com/show_bug.cgi?id=1313686
- https://lists.debian.org/debian-lts-announce/2018/11/msg00038.html
- https://lists.gnu.org/archive/html/qemu-devel/2016-04/msg01106.html
- https://lists.gnu.org/archive/html/qemu-devel/2016-04/msg01118.html
- https://security.gentoo.org/glsa/201609-01
- http://git.qemu.org/?p=qemu.git%3Ba=commit%3Bh=691a02e2ce0c413236a78dee6f2651c937b09fb0
- http://www.securityfocus.com/bid/86067
- http://www.ubuntu.com/usn/USN-2974-1
- https://access.redhat.com/errata/RHSA-2017:1856
- https://access.redhat.com/errata/RHSA-2017:2392
- https://access.redhat.com/errata/RHSA-2017:2408
- https://bugzilla.redhat.com/show_bug.cgi?id=1313686
- https://lists.debian.org/debian-lts-announce/2018/11/msg00038.html
- https://lists.gnu.org/archive/html/qemu-devel/2016-04/msg01106.html
- https://lists.gnu.org/archive/html/qemu-devel/2016-04/msg01118.html
- https://security.gentoo.org/glsa/201609-01