Gentoo: GLSA-201810-05: xkbcommon: Multiple vulnerabilities
Summary
Multiple vulnerabilities have been discovered in libxkbcommon. Please review the CVE identifiers referenced below for details.
Resolution
All libxkbcommon users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=x11-libs/libxkbcommon-0.8.2"
References
[ 1 ] CVE-2018-15853 https://nvd.nist.gov/vuln/detail/CVE-2018-15853 [ 2 ] CVE-2018-15854 https://nvd.nist.gov/vuln/detail/CVE-2018-15854 [ 3 ] CVE-2018-15855 https://nvd.nist.gov/vuln/detail/CVE-2018-15855 [ 4 ] CVE-2018-15856 https://nvd.nist.gov/vuln/detail/CVE-2018-15856 [ 5 ] CVE-2018-15857 https://nvd.nist.gov/vuln/detail/CVE-2018-15857 [ 6 ] CVE-2018-15858 https://nvd.nist.gov/vuln/detail/CVE-2018-15858 [ 7 ] CVE-2018-15859 https://nvd.nist.gov/vuln/detail/CVE-2018-15859 [ 8 ] CVE-2018-15861 https://nvd.nist.gov/vuln/detail/CVE-2018-15861 [ 9 ] CVE-2018-15862 https://nvd.nist.gov/vuln/detail/CVE-2018-15862 [ 10 ] CVE-2018-15863 https://nvd.nist.gov/vuln/detail/CVE-2018-15863 [ 11 ] CVE-2018-15864 https://nvd.nist.gov/vuln/detail/CVE-2018-15864
Availability
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201810-05
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
xkbcommon is a library to handle keyboard descriptions, including loading them from disk, parsing them and handling their state.
Affected Packages
------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 x11-libs/libxkbcommon < 0.8.2 >= 0.8.2
Impact
===== A local attacker could supply a specially crafted keymap file possibly resulting in a Denial of Service condition.
Workaround
There is no known workaround at this time.