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.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Xen | Xen | 4.0.0 (including) | 4.0.0 (including) |
| Xen | Xen | 4.0.1 (including) | 4.0.1 (including) |
| Xen | Xen | 4.0.2 (including) | 4.0.2 (including) |
| Xen | Xen | 4.0.3 (including) | 4.0.3 (including) |
| Xen | Xen | 4.0.4 (including) | 4.0.4 (including) |
| Xen | Xen | 4.1.0 (including) | 4.1.0 (including) |
| Xen | Xen | 4.1.1 (including) | 4.1.1 (including) |
| Xen | Xen | 4.1.2 (including) | 4.1.2 (including) |
| Xen | Xen | 4.1.3 (including) | 4.1.3 (including) |
| Xen | Xen | 4.1.4 (including) | 4.1.4 (including) |
| Xen | Xen | 4.1.5 (including) | 4.1.5 (including) |
| Xen | Xen | 4.1.6 (including) | 4.1.6 (including) |
| Xen | Xen | 4.1.6.1 (including) | 4.1.6.1 (including) |
| Xen | Xen | 4.2.0 (including) | 4.2.0 (including) |
| Xen | Xen | 4.2.1 (including) | 4.2.1 (including) |
| Xen | Xen | 4.2.2 (including) | 4.2.2 (including) |
| Xen | Xen | 4.2.3 (including) | 4.2.3 (including) |
| Xen | Xen | 4.2.4 (including) | 4.2.4 (including) |
| Xen | Xen | 4.2.5 (including) | 4.2.5 (including) |
| Xen | Xen | 4.3.0 (including) | 4.3.0 (including) |
| Xen | Xen | 4.3.1 (including) | 4.3.1 (including) |
| Xen | Xen | 4.3.2 (including) | 4.3.2 (including) |
| Xen | Xen | 4.3.3 (including) | 4.3.3 (including) |
| Xen | Xen | 4.3.4 (including) | 4.3.4 (including) |
| Xen | Xen | 4.4.0 (including) | 4.4.0 (including) |
| Xen | Xen | 4.4.0-rc1 (including) | 4.4.0-rc1 (including) |
| Xen | Xen | 4.4.1 (including) | 4.4.1 (including) |
| Xen | Xen | 4.4.2 (including) | 4.4.2 (including) |
| Xen | Xen | 4.4.3 (including) | 4.4.3 (including) |
| Xen | Xen | 4.4.4 (including) | 4.4.4 (including) |
| Xen | Xen | 4.5.0 (including) | 4.5.0 (including) |
| Xen | Xen | 4.5.1 (including) | 4.5.1 (including) |
| Xen | Xen | 4.5.2 (including) | 4.5.2 (including) |
| Xen | Xen | 4.5.3 (including) | 4.5.3 (including) |
| Xen | Xen | 4.6.0 (including) | 4.6.0 (including) |
| Xen | Xen | 4.6.1 (including) | 4.6.1 (including) |
| Xen | Ubuntu | devel | * |
| Xen | Ubuntu | precise | * |
| Xen | Ubuntu | trusty | * |
| Xen | Ubuntu | wily | * |
| Xen | Ubuntu | xenial | * |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: