Gentoo: GLSA-202006-08: WebKitGTK+: Multiple vulnerabilities
Summary
Multiple vulnerabilities have been discovered in WebKitGTK+. Please review the CVE identifiers referenced below for details.
Resolution
All WebKitGTK+ users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=net-libs/webkit-gtk-2.28.2"
References
[ 1 ] CVE-2020-10018 https://nvd.nist.gov/vuln/detail/CVE-2020-10018 [ 2 ] CVE-2020-10018 https://nvd.nist.gov/vuln/detail/CVE-2020-10018 [ 3 ] CVE-2020-11793 https://nvd.nist.gov/vuln/detail/CVE-2020-11793 [ 4 ] CVE-2020-11793 https://nvd.nist.gov/vuln/detail/CVE-2020-11793 [ 5 ] CVE-2020-3885 https://nvd.nist.gov/vuln/detail/CVE-2020-3885 [ 6 ] CVE-2020-3894 https://nvd.nist.gov/vuln/detail/CVE-2020-3894 [ 7 ] CVE-2020-3895 https://nvd.nist.gov/vuln/detail/CVE-2020-3895 [ 8 ] CVE-2020-3897 https://nvd.nist.gov/vuln/detail/CVE-2020-3897 [ 9 ] CVE-2020-3899 https://nvd.nist.gov/vuln/detail/CVE-2020-3899 [ 10 ] CVE-2020-3900 https://nvd.nist.gov/vuln/detail/CVE-2020-3900 [ 11 ] CVE-2020-3901 https://nvd.nist.gov/vuln/detail/CVE-2020-3901 [ 12 ] CVE-2020-3902 https://nvd.nist.gov/vuln/detail/CVE-2020-3902
Availability
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/202006-08
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
WebKitGTK+ is a full-featured port of the WebKit rendering engine, suitable for projects requiring any kind of web integration, from hybrid HTML/CSS applications to full-fledged web browsers.
Affected Packages
------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 net-libs/webkit-gtk < 2.28.2 >= 2.28.2
Impact
===== Please review the referenced CVE identifiers for details.
Workaround
There is no known workaround at this time.