CVE-2020-2732 - log back

CVE-2020-2732 edited at 08 Mar 2020 11:53:21
Description
- An issue has been found in KVM before 5.6-rc4, 5.5.7 and 5.4.23, where vmx_check_intercept ws is not yet fully implemented on Intel processors, causing e.g. the I/O or MSR interception bitmaps not to be checked. This in turn allowed the L2 guest to trick the L0 hypervisor into accessing sensitive information on the L1 hypervisor.
+ An issue has been found in KVM before 5.5.7, where vmx_check_intercept ws is not yet fully implemented on Intel processors, causing e.g. the I/O or MSR interception bitmaps not to be checked. This in turn allowed the L2 guest to trick the L0 hypervisor into accessing sensitive information on the L1 hypervisor.
CVE-2020-2732 edited at 06 Mar 2020 09:39:33
Description
- An issue has been found in KVM, where vmx_check_intercept ws is not yet fully implemented on Intel processors, causing e.g. the I/O or MSR interception bitmaps not to be checked. This in turn allowed the L2 guest to trick the L0 hypervisor into accessing sensitive information on the L1 hypervisor.
+ An issue has been found in KVM before 5.6-rc4, 5.5.7 and 5.4.23, where vmx_check_intercept ws is not yet fully implemented on Intel processors, causing e.g. the I/O or MSR interception bitmaps not to be checked. This in turn allowed the L2 guest to trick the L0 hypervisor into accessing sensitive information on the L1 hypervisor.
CVE-2020-2732 edited at 06 Mar 2020 09:19:22
Description
- vmx_check_intercept ws not yet fully implemented by KVM on Intel processors, causing e.g. the I/O or MSR interception bitmaps not to be checked this in turn allowed the L2 guest to trick the L0 hypervisor into accessing sensitive information on the L1 hypervisor.
+ An issue has been found in KVM, where vmx_check_intercept ws is not yet fully implemented on Intel processors, causing e.g. the I/O or MSR interception bitmaps not to be checked. This in turn allowed the L2 guest to trick the L0 hypervisor into accessing sensitive information on the L1 hypervisor.
References
+ https://www.openwall.com/lists/oss-security/2020/02/25/3
+ https://www.spinics.net/lists/kvm/msg208259.html
+ https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=07721feee46b4b248402133228235318199b05ec
+ https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=35a571346a94fb93b5b3b6a599675ef3384bc75c
+ https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e71237d3ff1abf9f3388337cfebf53b96df2020d
CVE-2020-2732 edited at 06 Mar 2020 00:35:04
Severity
- Unknown
+ High
Remote
- Unknown
+ Local
Type
- Unknown
+ Information disclosure
Description
+ vmx_check_intercept ws not yet fully implemented by KVM on Intel processors, causing e.g. the I/O or MSR interception bitmaps not to be checked this in turn allowed the L2 guest to trick the L0 hypervisor into accessing sensitive information on the L1 hypervisor.
References
Notes
CVE-2020-2732 created at 06 Mar 2020 00:28:26