Bug 1788842 (CVE-2019-19924) - CVE-2019-19924 sqlite: incorrect sqlite3WindowRewrite() error handling leads to mishandling certain parser-tree rewriting
Summary: CVE-2019-19924 sqlite: incorrect sqlite3WindowRewrite() error handling leads ...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2019-19924
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1788843 1789773 1789775 1789776
Blocks: 1788845
TreeView+ depends on / blocked
 
Reported: 2020-01-08 08:48 UTC by Marian Rehak
Modified: 2020-04-28 16:35 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 16:35:14 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:1810 0 None None None 2020-04-28 15:55:22 UTC

Description Marian Rehak 2020-01-08 08:48:45 UTC
SQLite 3.30.1 mishandles certain parser-tree rewriting, related to expr.c, vdbeaux.c, and window.c. This is caused by incorrect sqlite3WindowRewrite() error handling.

Upstream fix:

https://github.com/sqlite/sqlite/commit/8654186b0236d556aa85528c2573ee0b6ab71be3

Comment 1 Marian Rehak 2020-01-08 08:49:17 UTC
Created sqlite tracking bugs for this issue:

Affects: fedora-30 [bug 1788843]

Comment 3 Huzaifa S. Sidhpurwala 2020-01-10 12:19:33 UTC
Created sqlite tracking bugs for this issue:

Affects: fedora-31 [bug 1789773]

Comment 5 errata-xmlrpc 2020-04-28 15:55:20 UTC
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

Comment 6 Product Security DevOps Team 2020-04-28 16:35:14 UTC
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-19924


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