SPICE allows local guest OS users to read from or write to arbitrary host memory locations via crafted primary surface parameters, a similar issue to CVE-2015-5261.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Enterprise_linux | Redhat | 7.0 (including) | 7.0 (including) |
| Enterprise_linux_desktop | Redhat | 7.0 (including) | 7.0 (including) |
| Enterprise_linux_hpc_node_eus | Redhat | 7.2 (including) | 7.2 (including) |
| Enterprise_linux_server | Redhat | 7.0 (including) | 7.0 (including) |
| Enterprise_linux_server_aus | Redhat | 7.2 (including) | 7.2 (including) |
| Enterprise_linux_server_eus | Redhat | 7.2 (including) | 7.2 (including) |
| Enterprise_linux_workstation | Redhat | 7.0 (including) | 7.0 (including) |
| Red Hat Enterprise Linux 6 | RedHat | spice-server-0:0.12.4-13.el6.1 | * |
| Red Hat Enterprise Linux 7 | RedHat | spice-0:0.12.4-15.el7_2.1 | * |
| Spice | Ubuntu | devel | * |
| Spice | Ubuntu | precise | * |
| Spice | Ubuntu | trusty | * |
| Spice | Ubuntu | wily | * |
| Spice | Ubuntu | xenial | * |
| Spice | Ubuntu | yakkety | * |
| Spice | Ubuntu | zesty | * |
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: