CVE-2017-10916: Infoleak

Published Jul 5, 2017

Updated

The vCPU context-switch implementation in Xen through 4.8.x improperly interacts with the Memory Protection Extensions (MPX) and Protection Key (PKU) features, which makes it easier for guest OS users to defeat ASLR and other protection mechanisms, aka XSA-220.

Affected Software

13 affected components

XEN Xen=4.5.0

XEN Xen=4.5.1

XEN Xen=4.5.2

XEN Xen=4.5.3

XEN Xen=4.5.5

XEN Xen=4.6.0

XEN Xen=4.6.1

XEN Xen=4.6.2

XEN Xen=4.6.4

XEN Xen=4.6.5

XEN Xen=4.7.1

XEN Xen=4.8.0

XEN Xen=4.8.1

Event History

Jul 5, 2017

CVE Published

via MITRE·01:00 AM

Data Sourced

via MITRE·01:00 AM

Description

Frequently Asked Questions

What is the severity of CVE-2017-10916?

CVE-2017-10916 is classified as a medium-severity vulnerability due to its potential to weaken memory protection mechanisms.

How do I fix CVE-2017-10916?

To fix CVE-2017-10916, upgrade to a Xen version that is patched against this vulnerability.

What systems are affected by CVE-2017-10916?

CVE-2017-10916 affects various versions of Xen, specifically versions 4.5.0 to 4.8.1.

What types of attacks can exploit CVE-2017-10916?

CVE-2017-10916 can be exploited by guest OS users to bypass ASLR and other security protections.

What are the implications of CVE-2017-10916 in a virtualized environment?

CVE-2017-10916 may allow attackers to undermine the isolation between virtual machines, potentially leading to data breaches.