Bug 1659363 - sqlite: Multiple security flaws in sqlite triggered via corrupted database files (Magellan)
Summary: sqlite: Multiple security flaws in sqlite triggered via corrupted database fi...
Keywords:
Status: CLOSED DUPLICATE of bug 1659379
Alias: None
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-14 08:11 UTC by Huzaifa S. Sidhpurwala
Modified: 2019-09-29 15:04 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-12-15 04:35:38 UTC
Embargoed:


Attachments (Terms of Use)

Description Huzaifa S. Sidhpurwala 2018-12-14 08:11:33 UTC
As per: 

https://blade.tencent.com/magellan/index_en.html
https://chromereleases.googleblog.com/2018/12/stable-channel-update-for-desktop.html

Multiple flaws were found in sqlite. An attacker who could run arbitrary SQL command, could corrupt the internal databases and execute arbitrary code as the user running the application.

Upstream release sqlite-3.25.3 to address the changes:
https://www.sqlite.org/releaselog/3_25_3.html

Also sqlite-3.26 introduces defense-in-depth changes. This needs to be enabled by setting SQLITE_DBCONFIG_DEFENSIVE in the config file. This may break compatibility with certain applications which try to write to sqlite internal database files.
https://www.sqlite.org/releaselog/3_26_0.html
https://sqlite.org/src/info/11d98414eac467af

Comment 2 Huzaifa S. Sidhpurwala 2018-12-15 04:35:38 UTC

*** This bug has been marked as a duplicate of bug 1659379 ***


Note You need to log in before you can comment on or make changes to this bug.