Bug 1787032 (CVE-2019-19880)

Summary: CVE-2019-19880 sqlite: invalid pointer dereference in exprListAppendList in window.c
Product: [Other] Security Response Reporter: Guilherme de Almeida Suckevicz <gsuckevi>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: databases-maint, drizt72, erack, erik-fedora, fedora, huzaifas, itamar, mschorm, odubaj, pkubat, praiskup, rh-spice-bugs, rjones, wilmer5
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-17 14:10:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1787034, 1787035, 1787036, 1787528, 1787529, 1801837    
Bug Blocks: 1787037    

Description Guilherme de Almeida Suckevicz 2019-12-30 13:49:44 UTC
exprListAppendList in window.c in SQLite 3.30.1 allows attackers to trigger an invalid pointer dereference because constant integer values in ORDER BY clauses of window definitions are mishandled.

Reference and upstream commit:

Comment 1 Guilherme de Almeida Suckevicz 2019-12-30 13:51:06 UTC
Created mingw-sqlite tracking bugs for this issue:

Affects: epel-7 [bug 1787036]
Affects: fedora-all [bug 1787034]

Created sqlite tracking bugs for this issue:

Affects: fedora-all [bug 1787035]

Comment 2 Huzaifa S. Sidhpurwala 2020-01-03 09:27:54 UTC
This is basically crash when processing certain integer values in a ORDER statement.

Comment 4 errata-xmlrpc 2020-02-17 08:24:32 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6 Supplementary

Via RHSA-2020:0514 https://access.redhat.com/errata/RHSA-2020:0514

Comment 5 Product Security DevOps Team 2020-02-17 14:10:05 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):