First published: Tue Jun 07 2016(Updated: )
The libxl device-handling in Xen through 4.6.x allows local guest OS users with access to the driver domain to cause a denial of service (management tool confusion) by manipulating information in the backend directories in xenstore.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Xen xen-unstable | =4.0.0 | |
Xen xen-unstable | =4.0.1 | |
Xen xen-unstable | =4.0.2 | |
Xen xen-unstable | =4.0.3 | |
Xen xen-unstable | =4.0.4 | |
Xen xen-unstable | =4.1.0 | |
Xen xen-unstable | =4.1.1 | |
Xen xen-unstable | =4.1.2 | |
Xen xen-unstable | =4.1.3 | |
Xen xen-unstable | =4.1.4 | |
Xen xen-unstable | =4.1.5 | |
Xen xen-unstable | =4.1.6 | |
Xen xen-unstable | =4.1.6.1 | |
Xen xen-unstable | =4.2.0 | |
Xen xen-unstable | =4.2.1 | |
Xen xen-unstable | =4.2.2 | |
Xen xen-unstable | =4.2.3 | |
Xen xen-unstable | =4.2.4 | |
Xen xen-unstable | =4.2.5 | |
Xen xen-unstable | =4.3.0 | |
Xen xen-unstable | =4.3.1 | |
Xen xen-unstable | =4.3.2 | |
Xen xen-unstable | =4.3.3 | |
Xen xen-unstable | =4.3.4 | |
Xen xen-unstable | =4.4.0 | |
Xen xen-unstable | =4.4.0-rc1 | |
Xen xen-unstable | =4.4.1 | |
Xen xen-unstable | =4.4.2 | |
Xen xen-unstable | =4.4.3 | |
Xen xen-unstable | =4.4.4 | |
Xen xen-unstable | =4.5.0 | |
Xen xen-unstable | =4.5.1 | |
Xen xen-unstable | =4.5.2 | |
Xen xen-unstable | =4.5.3 | |
Xen xen-unstable | =4.6.0 | |
Xen xen-unstable | =4.6.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2016-4963 is considered moderate, as it allows denial of service specifically affecting management tool operation in vulnerable Xen versions.
CVE-2016-4963 allows local guest OS users to manipulate xenstore backend directories, potentially causing confusion in management tools and leading to a denial of service.
CVE-2016-4963 affects Xen versions from 4.0.0 to 4.6.1, including all versions in between.
To fix CVE-2016-4963, update your Xen installation to a version beyond 4.6.1 where the vulnerability has been addressed.
There are no specific mitigations other than upgrading to an unaffected version of Xen to resolve CVE-2016-4963.