Gentoo: GLSA-202107-49: Chromium, Google Chrome: Multiple vulnerabilities
Summary
Multiple vulnerabilities have been discovered in chromium, and google-chrome. Please review the CVE identifiers referenced below for details.
Resolution
All Chromium users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot -v ">=www-client/chromium-91.0.4472.164"
All Google Chrome users should upgrade to the latest version:
# emerge --sync
# emerge -a --oneshot -v ">=www-client/google-chrome-91.0.4472.164"
References
[ 1 ] CVE-2021-30541 https://nvd.nist.gov/vuln/detail/CVE-2021-30541 [ 2 ] CVE-2021-30559 https://nvd.nist.gov/vuln/detail/CVE-2021-30559 [ 3 ] CVE-2021-30560 https://nvd.nist.gov/vuln/detail/CVE-2021-30560 [ 4 ] CVE-2021-30561 https://nvd.nist.gov/vuln/detail/CVE-2021-30561 [ 5 ] CVE-2021-30562 https://nvd.nist.gov/vuln/detail/CVE-2021-30562 [ 6 ] CVE-2021-30563 https://nvd.nist.gov/vuln/detail/CVE-2021-30563 [ 7 ] CVE-2021-30564 https://nvd.nist.gov/vuln/detail/CVE-2021-30564
Availability
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/202107-49
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
Chromium is an open-source browser project that aims to build a safer,
faster, and more stable way for all users to experience the web.
Google Chrome is one fast, simple, and secure browser for all your
devices.
Affected Packages
------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 www-client/chromium < 91.0.4472.164 >= 91.0.4472.164 2 www-client/google-chrome < 91.0.4472.164 >= 91.0.4472.164 ------------------------------------------------------------------- 2 affected packages
Impact
===== Please review the referenced CVE identifiers for details.
Workaround
There is no known workaround at this time.