Alerts This Week
Warning Icon 1 764
Alerts This Week
Warning Icon 1 764

Gentoo: GLSA-202211-12 Urgent: openssl Security Flaw Poses System Threat

gentoo
Calendar Grey October 16, 2022
Dist Gentoo Esm H88
Numerous security flaws found in libxml2 may result in unauthorized code execution. Updating is advised for protection.
Multiple vulnerabilities have been discovered in libxml2, the worst of which could result in arbitrary code execution.

Summary

Multiple vulnerabilities have been discovered in libxml2. Please review the CVE identifiers referenced below for details.

Resolution

All libxml2 users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=dev-libs/libxml2-2.10.2"

References

[ 1 ] CVE-2022-23308 https://nvd.nist.gov/vuln/detail/CVE-2022-23308 [ 2 ] CVE-2022-29824 https://nvd.nist.gov/vuln/detail/CVE-2022-29824

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/202210-03
style>.gentoo_availability{display:block;}

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.

Severity: High
Title: libxml2: Multiple Vulnerabilities
Date: October 16, 2022
Bugs: #833809, #842261, #865727
ID: 202210-03

Synopsis

Multiple vulnerabilities have been discovered in libxml2, the worst of which could result in arbitrary code execution.

Background

libxml2 is the XML C parser and toolkit developed for the GNOME project.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 dev-libs/libxml2 < 2.10.2 >= 2.10.2

Impact

===== Please review the referenced CVE identifiers for details.

Workaround

There is no known workaround at this time.

Your message here