CVE-2020-11741

An issue was discovered in xenoprof in Xen through 4.13.x, allowing guest OS users (with active profiling) to obtain sensitive information about other guests, cause a denial of service, or possibly gain privileges. For guests for which "active" profiling was enabled by the administrator, the xenoprof code uses the standard Xen shared ring structure. Unfortunately, this code did not treat the guest as a potential adversary: it trusts the guest not to modify buffer size information or modify head / tail pointers in unexpected ways. This can crash the host (DoS). Privilege escalation cannot be ruled out.

An issue was discovered in xenoprof in Xen through 4.13.x, allowing guest OS users (with active profiling) to obtain sensitive information about other guests, cause a denial of service, or possibly gain privileges. For guests for which "active" profiling was enabled by the administrator, the xenoprof code uses the standard Xen shared ring structure. Unfortunately, this code did not treat the guest as a potential adversary: it trusts the guest not to modify buffer size information or modify head / tail pointers in unexpected ways. This can crash the host (DoS). Privilege escalation cannot be ruled out.

Se detectó un problema en xenoprof en Xen versiones hasta 4.13.x, que permitía a usuarios invitados del Sistema Operativo (con perfiles activos) obtener información confidencial sobre otros invitados, causar una denegación de servicio o posiblemente alcanzar privilegios. Para aquellos invitados a los que el administrador habilitó la creación de perfiles "active", el código xenoprof usa la estructura de anillo compartida de Xen estándar. Desafortunadamente, este código no trató al invitado como un adversario potencial: confía en que el invitado no modificará la información del tamaño del búfer ni modificará los punteros de cabeza y cola de forma inesperada. Esto puede bloquear el host (DoS). La escalada de privilegios no puede ser descartada.