Gentoo: GLSA-202101-15: VirtualBox: Multiple vulnerabilities
Summary
Multiple vulnerabilities have been discovered in VirtualBox. Please review the CVE identifiers referenced below for details.
Resolution
All VirtualBox users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot -v ">=app-emulation/virtualbox-6.1.18"
References
[ 1 ] CVE-2020-14872 https://nvd.nist.gov/vuln/detail/CVE-2020-14872 [ 2 ] CVE-2020-14881 https://nvd.nist.gov/vuln/detail/CVE-2020-14881 [ 3 ] CVE-2020-14884 https://nvd.nist.gov/vuln/detail/CVE-2020-14884 [ 4 ] CVE-2020-14885 https://nvd.nist.gov/vuln/detail/CVE-2020-14885 [ 5 ] CVE-2020-14886 https://nvd.nist.gov/vuln/detail/CVE-2020-14886 [ 6 ] CVE-2020-14889 https://nvd.nist.gov/vuln/detail/CVE-2020-14889 [ 7 ] CVE-2020-14892 https://nvd.nist.gov/vuln/detail/CVE-2020-14892 [ 8 ] CVE-2021-2073 https://nvd.nist.gov/vuln/detail/CVE-2021-2073 [ 9 ] CVE-2021-2074 https://nvd.nist.gov/vuln/detail/CVE-2021-2074 [ 10 ] CVE-2021-2086 https://nvd.nist.gov/vuln/detail/CVE-2021-2086 [ 11 ] CVE-2021-2111 https://nvd.nist.gov/vuln/detail/CVE-2021-2111 [ 12 ] CVE-2021-2112 https://nvd.nist.gov/vuln/detail/CVE-2021-2112 [ 13 ] CVE-2021-2119 https://nvd.nist.gov/vuln/detail/CVE-2021-2119 [ 14 ] C...
Availability
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/202101-15
Concerns
Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.
Background
VirtualBox is a powerful virtualization product from Oracle.
Affected Packages
------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 app-emulation/virtualbox < 6.1.18 >= 6.1.18
Impact
===== Please review the referenced CVE identifiers for details.
Workaround
There is no known workaround at this time.