First published: Fri Dec 14 2018(Updated: )
Multiple flaws were found in sqlite. An attacker who is able to run arbitrary SQL statements could use this flaw to corrupt the internal databases, which can lead to arbitrary code execution as the user running sqlite. This issue was fixed via sqlite-3.25.3 release at: <a href="https://www.sqlite.org/releaselog/3_25_3.html">https://www.sqlite.org/releaselog/3_25_3.html</a> Also sqlite-3.36 introduced SQLITE_DBCONFIG_DEFENSIVE option which when added to the config file, could prevent attackers for corrupting the internal database files. This could however break applications which require users to write these database files. <a href="https://www.sqlite.org/releaselog/3_26_0.html">https://www.sqlite.org/releaselog/3_26_0.html</a> <a href="https://www.sqlite.org/c3ref/c_dbconfig_defensive.html#sqlitedbconfigdefensive">https://www.sqlite.org/c3ref/c_dbconfig_defensive.html#sqlitedbconfigdefensive</a>
Affected Software | Affected Version | How to fix |
---|---|---|
SQLite JDBC | <3.25.3>=3.25.3<3.36 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-1659379 is critical due to the potential for arbitrary code execution.
To fix REDHAT-BUG-1659379, update SQLite to version 3.25.3 or later.
The affected products by REDHAT-BUG-1659379 include SQLite versions prior to 3.25.3 and between 3.25.3 and 3.36.
An attacker can run arbitrary SQL statements that could corrupt internal databases due to REDHAT-BUG-1659379.
Exploitation of REDHAT-BUG-1659379 could lead to arbitrary code execution with the privileges of the SQLite process.