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

Gentoo GLSA-202210-40 High: SQLite Multiple Code Execution Risks

gentoo
Calendar Grey October 31, 2022
Dist Gentoo Esm H88
Gentoo Linux advisory GLSA 202210-41 addresses critical SQLite flaws that may result in arbitrary code execution.
Multiple vulnerabilities have been found in SQLite, the worst of which could result in arbitrary code execution.

Summary

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

Resolution

All SQLite users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=dev-db/sqlite-3.39.2"

References

[ 1 ] CVE-2021-20227 https://nvd.nist.gov/vuln/detail/CVE-2021-20227 [ 2 ] CVE-2022-35737 https://nvd.nist.gov/vuln/detail/CVE-2022-35737

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/202210-40
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: SQLite: Multiple Vulnerabilities
Date: October 31, 2022
Bugs: #777990, #863431
ID: 202210-40

Synopsis

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

Background

SQLite is a C library that implements an SQL database engine.

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-db/sqlite < 3.39.2 >= 3.39.2

Impact

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

Workaround

There is no known workaround at this time.

Your message here