Alerts This Week
Warning Icon 1 770
Alerts This Week
Warning Icon 1 770

Gentoo: GLSA-202210-39 High: libxml2 Threats and Code Execution Risks

gentoo
Calendar Grey October 31, 2022
Dist Gentoo Esm H88
Uncover critical libxml2 flaws impacting Gentoo Linux and learn the measures necessary to strengthen your system's defenses.
Multiple vulnerabilities have been found 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.3"

References

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

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/202210-39
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 31, 2022
Bugs: #877149
ID: 202210-39

Synopsis

Multiple vulnerabilities have been found 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.3 >= 2.10.3

Impact

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

Workaround

There is no known workaround at this time.

Your message here