An out of bounds read flaw was found in the SQLite component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=1025471 External References: https://chromereleases.googleblog.com/2019/12/stable-channel-update-for-desktop.html
Created chromium tracking bugs for this issue: Affects: epel-7 [bug 1782013] Affects: fedora-all [bug 1782012]
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Supplementary Via RHSA-2019:4238 https://access.redhat.com/errata/RHSA-2019:4238
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2019-13753
While the chromium bug is not public yet, its id leads us to this: https://chromium.googlesource.com/chromium/src/third_party/sqlite/+/47bd97d715260127c995d92dde8dd8adb669b6b3 https://chromium.googlesource.com/chromium/src/third_party/sqlite/+/47bd97d715260127c995d92dde8dd8adb669b6b3/patches/0004-Remove-reachable-NEVER-in-fts3.patch which further leads us to upstream commit: https://www.sqlite.org/src/info/8bd75bf636f72f32 https://github.com/sqlite/sqlite/commit/fd6bf04bba8035836e8f92771d277a4e868c6299 There is no released sqlite version with the fix yet.
This is related to CVE-2019-13752. The only difference being that CVE-2019-13752 is related to fts3NodeAddTerm, while this CVE is related to fts3IncrmergePush. The patch described in comment #5 needs to be applied after the CVE-2019-13752 patch.
Created mingw-sqlite tracking bugs for this issue: Affects: epel-all [bug 1786533] Affects: fedora-all [bug 1786532] Created sqlite tracking bugs for this issue: Affects: fedora-all [bug 1786531]
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2020:1810 https://access.redhat.com/errata/RHSA-2020:1810