A pointer disclosure flaw was found in the SQLite component of the Chromium browser. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=742407 External References: https://chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html
Created chromium tracking bugs for this issue: Affects: fedora-all [bug 1475216]
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Supplementary Via RHSA-2017:1833 https://access.redhat.com/errata/RHSA-2017:1833
The chromium bug is private, but looking at the commit: https://chromium.googlesource.com/chromium/src.git/+/3bfe67c9c4b45eb713326aae7a67c8f7390dae08 Which leads to the upstream commit at: https://www.sqlite.org/src/info/d6a44b352d432d52 It seems that this issue is not specific to chromium-browser, but affects versions of sqlite shipped with Red Hat Enterprise Linux and Fedora. This flaw basically causes sqlite to leak the underlying memory location, when some operations are performed. This memory-address leak can be used by other (more severe) flaws to potentially result in code-execution. The patch adds new API functions, "sqlite3_bind_pointer(), sqlite3_result_pointer(), and sqlite3_value_pointer() used to safely move pointer values through SQL without exposing underlying memory address information." This patch is included in the sqlite-3.20.0 release. More details about the new API (interfaces) and how they can be used is available at: https://www.sqlite.org/bindptr.html
Created sqlite tracking bugs for this issue: Affects: fedora-all [bug 1478785]
Created sqlite2 tracking bugs for this issue: Affects: fedora-all [bug 1478786]
Created mingw-sqlite tracking bugs for this issue: Affects: fedora-all [bug 1478787]