CVE-2019-19925

zipfileUpdate in ext/misc/zipfile.c in SQLite 3.30.1 mishandles a NULL pathname during an update of a ZIP archive.

Chromium-browser 80.0.3987.122 fixes security issues:

Multiple flaws were found in the way Chromium 79.0.3945.130 processes various types of web content, where loading a web page containing malicious content could cause Chromium to crash, execute arbitrary code, or disclose sensitive information. (CVE-2020-6381, CVE-2020-6382, CVE-2020-6383, CVE-2020-6384, CVE-2020-6385, CVE-2020-6386, CVE-2020-6387, CVE-2020-6388, CVE-2020-6389, CVE-2020-6390, CVE-2020-6391, CVE-2020-6392, CVE-2020-6393, CVE-2020-6394, CVE-2020-6395, CVE-2020-6396, CVE-2020-6397, CVE-2020-6398, CVE-2020-6399, CVE-2020-6400, CVE-2020-6401, CVE-2020-6402, CVE-2020-6403, CVE-2020-6404, CVE-2020-6405, CVE-2020-6406, CVE-2020-6407, CVE-2020-6408, CVE-2020-6409, CVE-2020-6410, CVE-2020-6411, CVE-2020-6412, CVE-2020-6413, CVE-2020-6414, CVE-2020-6415, CVE-2020-6416, CVE-2020-6418, CVE-2019-18197, CVE-2019-19923, CVE-2019-19925, CVE-2019-19926)

Upstream chromium 80.0.3987.122 also includes a fix for an integer overflow issue in ICU. Since the chromium-browser-stable package is linked against the icu packages instead of using the ICU source code bundled with chromium upstream, this issue is fixed in the icu package.

This update for chromium fixes the following issues:

Chromium was updated to version 80.0.3987.87 (boo#1162833).

Security issues fixed:

• CVE-2020-6381: Integer overflow in JavaScript (boo#1162833).
• CVE-2020-6382: Type Confusion in JavaScript (boo#1162833).
• CVE-2019-18197: Multiple vulnerabilities in XML (boo#1162833).
• CVE-2019-19926: Inappropriate implementation in SQLite (boo#1162833).
• CVE-2020-6385: Insufficient policy enforcement in storage (boo#1162833).
• CVE-2019-19880, CVE-2019-19925: Multiple vulnerabilities in SQLite (boo#1162833).
• CVE-2020-6387: Out of bounds write in WebRTC (boo#1162833).
• CVE-2020-6388: Out of bounds memory access in WebAudio (boo#1162833).
• CVE-2020-6389: Out of bounds write in WebRTC (boo#1162833).
• CVE-2020-6390: Out of bounds memory access in streams (boo#1162833).
• CVE-2020-6391: Insufficient validation of untrusted input in Blink (boo#1162833).
• CVE-2020-6392: Insufficient policy enforcement in extensions (boo#1162833).
• CVE-2020-6393: Insufficient policy enforcement in Blink (boo#1162833).
• CVE-2020-6394: Insufficient policy enforcement in Blink (boo#1162833).
• CVE-2020-6395: Out of bounds read in JavaScript (boo#1162833).
• CVE-2020-6396: Inappropriate implementation in Skia (boo#1162833).
• CVE-2020-6397: Incorrect security UI in sharing (boo#1162833).
• CVE-2020-6398: Uninitialized use in PDFium (boo#1162833).
• CVE-2020-6399: Insufficient policy enforcement in AppCache (boo#1162833).
• CVE-2020-6400: Inappropriate implementation in CORS (boo#1162833).
• CVE-2020-6401: Insufficient validation of untrusted input in Omnibox (boo#1162833).
• CVE-2020-6402: Insufficient policy enforcement in downloads (boo#1162833).
• CVE-2020-6403: Incorrect security UI in Omnibox (boo#1162833).
• CVE-2020-6404: Inappropriate implementation in Blink (boo#1162833).
• CVE-2020-6405: Out of bounds read in SQLite (boo#1162833).
• CVE-2020-6406: Use after free in audio (boo#1162833).
• CVE-2019-19923: Out of bounds memory access in SQLite (boo#1162833).
• CVE-2020-6408: Insufficient policy enforcement in CORS (boo#1162833).
• CVE-2020-6409: Inappropriate implementation in Omnibox (boo#1162833).
• CVE-2020-6410: Insufficient policy enforcement in navigation (boo#1162833).
• CVE-2020-6411: Insufficient validation of untrusted input in Omnibox (boo#1162833).
• CVE-2020-6412: Insufficient validation of untrusted input in Omnibox (boo#1162833).
• CVE-2020-6413: Inappropriate implementation in Blink (boo#1162833).
• CVE-2020-6414: Insufficient policy enforcement in Safe Browsing (boo#1162833).
• CVE-2020-6415: Inappropriate implementation in JavaScript (boo#1162833).
• CVE-2020-6416: Insufficient data validation in streams (boo#1162833).
• CVE-2020-6417: Inappropriate implementation in installer (boo#1162833).

This update for chromium fixes the following issues:

Chromium was updated to version 80.0.3987.87 (boo#1162833).

Security issues fixed:

• CVE-2020-6381: Integer overflow in JavaScript (boo#1162833).
• CVE-2020-6382: Type Confusion in JavaScript (boo#1162833).
• CVE-2019-18197: Multiple vulnerabilities in XML (boo#1162833).
• CVE-2019-19926: Inappropriate implementation in SQLite (boo#1162833).
• CVE-2020-6385: Insufficient policy enforcement in storage (boo#1162833).
• CVE-2019-19880, CVE-2019-19925: Multiple vulnerabilities in SQLite (boo#1162833).
• CVE-2020-6387: Out of bounds write in WebRTC (boo#1162833).
• CVE-2020-6388: Out of bounds memory access in WebAudio (boo#1162833).
• CVE-2020-6389: Out of bounds write in WebRTC (boo#1162833).
• CVE-2020-6390: Out of bounds memory access in streams (boo#1162833).
• CVE-2020-6391: Insufficient validation of untrusted input in Blink (boo#1162833).
• CVE-2020-6392: Insufficient policy enforcement in extensions (boo#1162833).
• CVE-2020-6393: Insufficient policy enforcement in Blink (boo#1162833).
• CVE-2020-6394: Insufficient policy enforcement in Blink (boo#1162833).
• CVE-2020-6395: Out of bounds read in JavaScript (boo#1162833).
• CVE-2020-6396: Inappropriate implementation in Skia (boo#1162833).
• CVE-2020-6397: Incorrect security UI in sharing (boo#1162833).
• CVE-2020-6398: Uninitialized use in PDFium (boo#1162833).
• CVE-2020-6399: Insufficient policy enforcement in AppCache (boo#1162833).
• CVE-2020-6400: Inappropriate implementation in CORS (boo#1162833).
• CVE-2020-6401: Insufficient validation of untrusted input in Omnibox (boo#1162833).
• CVE-2020-6402: Insufficient policy enforcement in downloads (boo#1162833).
• CVE-2020-6403: Incorrect security UI in Omnibox (boo#1162833).
• CVE-2020-6404: Inappropriate implementation in Blink (boo#1162833).
• CVE-2020-6405: Out of bounds read in SQLite (boo#1162833).
• CVE-2020-6406: Use after free in audio (boo#1162833).
• CVE-2019-19923: Out of bounds memory access in SQLite (boo#1162833).
• CVE-2020-6408: Insufficient policy enforcement in CORS (boo#1162833).
• CVE-2020-6409: Inappropriate implementation in Omnibox (boo#1162833).
• CVE-2020-6410: Insufficient policy enforcement in navigation (boo#1162833).
• CVE-2020-6411: Insufficient validation of untrusted input in Omnibox (boo#1162833).
• CVE-2020-6412: Insufficient validation of untrusted input in Omnibox (boo#1162833).
• CVE-2020-6413: Inappropriate implementation in Blink (boo#1162833).
• CVE-2020-6414: Insufficient policy enforcement in Safe Browsing (boo#1162833).
• CVE-2020-6415: Inappropriate implementation in JavaScript (boo#1162833).
• CVE-2020-6416: Insufficient data validation in streams (boo#1162833).
• CVE-2020-6417: Inappropriate implementation in installer (boo#1162833).

This update was imported from the openSUSE:Leap:15.1:Update update project.

This update for chromium, re2 fixes the following issues:

• Update to 80.0.3987.87 boo#1162833:
  • CVE-2020-6381: Integer overflow in JavaScript
  • CVE-2020-6382: Type Confusion in JavaScript
  • CVE-2019-18197: Multiple vulnerabilities in XML
  • CVE-2019-19926: Inappropriate implementation in SQLite
  • CVE-2020-6385: Insufficient policy enforcement in storage
  • CVE-2019-19880, CVE-2019-19925: Multiple vulnerabilities in SQLite
  • CVE-2020-6387: Out of bounds write in WebRTC
  • CVE-2020-6388: Out of bounds memory access in WebAudio
  • CVE-2020-6389: Out of bounds write in WebRTC
  • CVE-2020-6390: Out of bounds memory access in streams
  • CVE-2020-6391: Insufficient validation of untrusted input in Blink
  • CVE-2020-6392: Insufficient policy enforcement in extensions
  • CVE-2020-6393: Insufficient policy enforcement in Blink
  • CVE-2020-6394: Insufficient policy enforcement in Blink
  • CVE-2020-6395: Out of bounds read in JavaScript
  • CVE-2020-6396: Inappropriate implementation in Skia
  • CVE-2020-6397: Incorrect security UI in sharing
  • CVE-2020-6398: Uninitialized use in PDFium
  • CVE-2020-6399: Insufficient policy enforcement in AppCache
  • CVE-2020-6400: Inappropriate implementation in CORS
  • CVE-2020-6401: Insufficient validation of untrusted input in Omnibox
  • CVE-2020-6402: Insufficient policy enforcement in downloads
  • CVE-2020-6403: Incorrect security UI in Omnibox
  • CVE-2020-6404: Inappropriate implementation in Blink
  • CVE-2020-6405: Out of bounds read in SQLite
  • CVE-2020-6406: Use after free in audio
  • CVE-2019-19923: Out of bounds memory access in SQLite
  • CVE-2020-6408: Insufficient policy enforcement in CORS
  • CVE-2020-6409: Inappropriate implementation in Omnibox
  • CVE-2020-6410: Insufficient policy enforcement in navigation
  • CVE-2020-6411: Insufficient validation of untrusted input in Omnibox
  • CVE-2020-6412: Insufficient validation of untrusted input in Omnibox
  • CVE-2020-6413: Inappropriate implementation in Blink
  • CVE-2020-6414: Insufficient policy enforcement in Safe Browsing
  • CVE-2020-6415: Inappropriate implementation in JavaScript
  • CVE-2020-6416: Insufficient data validation in streams
  • CVE-2020-6417: Inappropriate implementation in installer

re2 was updated to fix:

Update to 2020-01-01:

• various developer visible changes

Update to 2019-12-01:

• fix latent bugs and undefined behavior

Update to 2019-11-01:

• new benchmark API

Update to 2019-09-01:

• build system fixes

Update to 2019-08-01:

• Update Unicode data to 12.1.0
• Various developer visible changes

Update to 2019-07-01:

• developer visible changes

This update for sqlite3 fixes the following issues:

• Update to version 3.36.0
• CVE-2020-15358: heap-based buffer overflow in multiSelectOrderBy due to mishandling of query-flattener optimization (bsc#1173641)
• CVE-2020-9327: NULL pointer dereference and segmentation fault because of generated column optimizations in isAuxiliaryVtabOperator (bsc#1164719)
• CVE-2019-20218: selectExpander in select.c proceeds with WITH stack unwinding even after a parsing error (bsc#1160439)
• CVE-2019-19959: memory-management error via ext/misc/zipfile.c involving embedded '\0' input (bsc#1160438)
• CVE-2019-19923: improper handling of certain uses of SELECT DISTINCT in flattenSubquery may lead to null pointer dereference (bsc#1160309)
• CVE-2019-19924: improper error handling in sqlite3WindowRewrite() (bsc#1159850)
• CVE-2019-19925: improper handling of NULL pathname during an update of a ZIP archive (bsc#1159847)
• CVE-2019-19926: improper handling of certain errors during parsing multiSelect in select.c (bsc#1159715)
• CVE-2019-19880: exprListAppendList in window.c allows attackers to trigger an invalid pointer dereference (bsc#1159491)
• CVE-2019-19603: during handling of CREATE TABLE and CREATE VIEW statements, does not consider confusion with a shadow table name (bsc#1158960)
• CVE-2019-19646: pragma.c mishandles NOT NULL in an integrity_check PRAGMA command in certain cases of generated columns (bsc#1158959)
• CVE-2019-19645: alter.c allows attackers to trigger infinite recursion via certain types of self-referential views in conjunction with ALTER TABLE statements (bsc#1158958)
• CVE-2019-19317: lookupName in resolve.c omits bits from the colUsed bitmask in the case of a generated column, which allows attackers to cause a denial of service (bsc#1158812)
• CVE-2019-19244: sqlite3,sqlite2,sqlite: The function sqlite3Select in select.c allows a crash if a sub-select uses both DISTINCT and window functions, and also has certain ORDER BY usage (bsc#1157818)
• CVE-2015-3415: sqlite3VdbeExec comparison operator vulnerability (bsc#928701)
• CVE-2015-3414: sqlite3,sqlite2: dequoting of collation-sequence names (bsc#928700)
• CVE-2020-13434: integer overflow in sqlite3_str_vappendf (bsc#1172115)
• CVE-2020-13630: (bsc#1172234: use-after-free in fts3EvalNextRow
• CVE-2020-13631: virtual table allowed to be renamed to one of its shadow tables (bsc#1172236)
• CVE-2020-13632: NULL pointer dereference via crafted matchinfo() query (bsc#1172240)
• CVE-2020-13435: Malicious SQL statements could have crashed the process that is running SQLite (bsc#1172091)

This update was imported from the SUSE:SLE-15:Update update project.

This update for sqlite3 fixes the following issues:

• Update to version 3.36.0
• CVE-2020-15358: heap-based buffer overflow in multiSelectOrderBy due to mishandling of query-flattener optimization (bsc#1173641)
• CVE-2020-9327: NULL pointer dereference and segmentation fault because of generated column optimizations in isAuxiliaryVtabOperator (bsc#1164719)
• CVE-2019-20218: selectExpander in select.c proceeds with WITH stack unwinding even after a parsing error (bsc#1160439)
• CVE-2019-19959: memory-management error via ext/misc/zipfile.c involving embedded '\0' input (bsc#1160438)
• CVE-2019-19923: improper handling of certain uses of SELECT DISTINCT in flattenSubquery may lead to null pointer dereference (bsc#1160309)
• CVE-2019-19924: improper error handling in sqlite3WindowRewrite() (bsc#1159850)
• CVE-2019-19925: improper handling of NULL pathname during an update of a ZIP archive (bsc#1159847)
• CVE-2019-19926: improper handling of certain errors during parsing multiSelect in select.c (bsc#1159715)
• CVE-2019-19880: exprListAppendList in window.c allows attackers to trigger an invalid pointer dereference (bsc#1159491)
• CVE-2019-19603: during handling of CREATE TABLE and CREATE VIEW statements, does not consider confusion with a shadow table name (bsc#1158960)
• CVE-2019-19646: pragma.c mishandles NOT NULL in an integrity_check PRAGMA command in certain cases of generated columns (bsc#1158959)
• CVE-2019-19645: alter.c allows attackers to trigger infinite recursion via certain types of self-referential views in conjunction with ALTER TABLE statements (bsc#1158958)
• CVE-2019-19317: lookupName in resolve.c omits bits from the colUsed bitmask in the case of a generated column, which allows attackers to cause a denial of service (bsc#1158812)
• CVE-2019-19244: sqlite3,sqlite2,sqlite: The function sqlite3Select in select.c allows a crash if a sub-select uses both DISTINCT and window functions, and also has certain ORDER BY usage (bsc#1157818)
• CVE-2015-3415: sqlite3VdbeExec comparison operator vulnerability (bsc#928701)
• CVE-2015-3414: sqlite3,sqlite2: dequoting of collation-sequence names (bsc#928700)
• CVE-2020-13434: integer overflow in sqlite3_str_vappendf (bsc#1172115)
• CVE-2020-13630: (bsc#1172234: use-after-free in fts3EvalNextRow
• CVE-2020-13631: virtual table allowed to be renamed to one of its shadow tables (bsc#1172236)
• CVE-2020-13632: NULL pointer dereference via crafted matchinfo() query (bsc#1172240)
• CVE-2020-13435: Malicious SQL statements could have crashed the process that is running SQLite (bsc#1172091)

This update for sqlite3 fixes the following issues:

• Update to version 3.36.0
• CVE-2020-15358: heap-based buffer overflow in multiSelectOrderBy due to mishandling of query-flattener optimization (bsc#1173641)
• CVE-2020-9327: NULL pointer dereference and segmentation fault because of generated column optimizations in isAuxiliaryVtabOperator (bsc#1164719)
• CVE-2019-20218: selectExpander in select.c proceeds with WITH stack unwinding even after a parsing error (bsc#1160439)
• CVE-2019-19959: memory-management error via ext/misc/zipfile.c involving embedded '\0' input (bsc#1160438)
• CVE-2019-19923: improper handling of certain uses of SELECT DISTINCT in flattenSubquery may lead to null pointer dereference (bsc#1160309)
• CVE-2019-19924: improper error handling in sqlite3WindowRewrite() (bsc#1159850)
• CVE-2019-19925: improper handling of NULL pathname during an update of a ZIP archive (bsc#1159847)
• CVE-2019-19926: improper handling of certain errors during parsing multiSelect in select.c (bsc#1159715)
• CVE-2019-19880: exprListAppendList in window.c allows attackers to trigger an invalid pointer dereference (bsc#1159491)
• CVE-2019-19603: during handling of CREATE TABLE and CREATE VIEW statements, does not consider confusion with a shadow table name (bsc#1158960)
• CVE-2019-19646: pragma.c mishandles NOT NULL in an integrity_check PRAGMA command in certain cases of generated columns (bsc#1158959)
• CVE-2019-19645: alter.c allows attackers to trigger infinite recursion via certain types of self-referential views in conjunction with ALTER TABLE statements (bsc#1158958)
• CVE-2019-19317: lookupName in resolve.c omits bits from the colUsed bitmask in the case of a generated column, which allows attackers to cause a denial of service (bsc#1158812)
• CVE-2019-19244: sqlite3,sqlite2,sqlite: The function sqlite3Select in select.c allows a crash if a sub-select uses both DISTINCT and window functions, and also has certain ORDER BY usage (bsc#1157818)
• CVE-2015-3415: sqlite3VdbeExec comparison operator vulnerability (bsc#928701)
• CVE-2015-3414: sqlite3,sqlite2: dequoting of collation-sequence names (bsc#928700)
• CVE-2020-13434: integer overflow in sqlite3_str_vappendf (bsc#1172115)
• CVE-2020-13630: (bsc#1172234: use-after-free in fts3EvalNextRow
• CVE-2020-13631: virtual table allowed to be renamed to one of its shadow tables (bsc#1172236)
• CVE-2020-13632: NULL pointer dereference via crafted matchinfo() query (bsc#1172240)
• CVE-2020-13435: Malicious SQL statements could have crashed the process that is running SQLite (bsc#1172091)

This update for sqlite3 fixes the following issues:

sqlite3 is sync version 3.36.0 from Factory (jsc#SLE-16032).

The following CVEs have been fixed in upstream releases up to this point, but were not mentioned in the change log so far:

• bsc#1173641, CVE-2020-15358: heap-based buffer overflow in multiSelectOrderBy due to mishandling of query-flattener optimization
• bsc#1164719, CVE-2020-9327: NULL pointer dereference and segmentation fault because of generated column optimizations in isAuxiliaryVtabOperator
• bsc#1160439, CVE-2019-20218: selectExpander in select.c proceeds with WITH stack unwinding even after a parsing error
• bsc#1160438, CVE-2019-19959: memory-management error via ext/misc/zipfile.c involving embedded '\0' input
• bsc#1160309, CVE-2019-19923: improper handling of certain uses of SELECT DISTINCT in flattenSubquery may lead to null pointer dereference
• bsc#1159850, CVE-2019-19924: improper error handling in sqlite3WindowRewrite()
• bsc#1159847, CVE-2019-19925: improper handling of NULL pathname during an update of a ZIP archive
• bsc#1159715, CVE-2019-19926: improper handling of certain errors during parsing multiSelect in select.c
• bsc#1159491, CVE-2019-19880: exprListAppendList in window.c allows attackers to trigger an invalid pointer dereference
• bsc#1158960, CVE-2019-19603: during handling of CREATE TABLE and CREATE VIEW statements, does not consider confusion with a shadow table name
• bsc#1158959, CVE-2019-19646: pragma.c mishandles NOT NULL in an integrity_check PRAGMA command in certain cases of generated columns
• bsc#1158958, CVE-2019-19645: alter.c allows attackers to trigger infinite recursion via certain types of self-referential views in conjunction with ALTER TABLE statements
• bsc#1158812, CVE-2019-19317: lookupName in resolve.c omits bits from the colUsed bitmask in the case of a generated column, which allows attackers to cause a denial of service
• bsc#1157818, CVE-2019-19244: sqlite3,sqlite2,sqlite: The function sqlite3Select in select.c allows a crash if a sub-select uses both DISTINCT and window functions, and also has certain ORDER BY usage
• bsc#928701, CVE-2015-3415: sqlite3VdbeExec comparison operator vulnerability
• bsc#928700, CVE-2015-3414: sqlite3,sqlite2: dequoting of collation-sequence names
• CVE-2020-13434 bsc#1172115: integer overflow in sqlite3_str_vappendf
• CVE-2020-13630 bsc#1172234: use-after-free in fts3EvalNextRow
• CVE-2020-13631 bsc#1172236: virtual table allowed to be renamed to one of its shadow tables
• CVE-2020-13632 bsc#1172240: NULL pointer dereference via crafted matchinfo() query
• CVE-2020-13435: Malicious SQL statements could have crashed the process that is running SQLite (bsc#1172091)

It was discovered that SQLite incorrectly handled certain shadow tables. An attacker could use this issue to cause SQLite to crash, resulting in a denial of service, or possibly execute arbitrary code. (CVE-2019-13734, CVE-2019-13750, CVE-2019-13753)

It was discovered that SQLite incorrectly handled certain corrupt records. An attacker could use this issue to cause SQLite to crash, resulting in a denial of service, or possibly execute arbitrary code. (CVE-2019-13751)

It was discovered that SQLite incorrectly handled certain queries. An attacker could use this issue to cause SQLite to crash, resulting in a denial of service, or possibly execute arbitrary code. This issue only affected Ubuntu 19.10. (CVE-2019-19880)

It was discovered that SQLite incorrectly handled certain queries. An attacker could use this issue to cause SQLite to crash, resulting in a denial of service, or possibly execute arbitrary code. This issue only affected Ubuntu 18.04 LTS and Ubuntu 19.10. (CVE-2019-19923)

It was discovered that SQLite incorrectly handled parser tree rewriting. An attacker could use this issue to cause SQLite to crash, resulting in a denial of service, or possibly execute arbitrary code. This issue only affected Ubuntu 19.10. (CVE-2019-19924)

It was discovered that SQLite incorrectly handled certain ZIP archives. An attacker could use this issue to cause SQLite to crash, resulting in a denial of service, or possibly execute arbitrary code. This issue only affected Ubuntu 18.04 LTS and Ubuntu 19.10. (CVE-2019-19925, CVE-2019-19959)

It was discovered that SQLite incorrectly handled errors during parsing. An attacker could use this issue to cause SQLite to crash, resulting in a denial of service, or possibly execute arbitrary code. (CVE-2019-19926)

It was discovered that SQLite incorrectly handled parsing errors. An attacker could use this issue to cause SQLite to crash, resulting in a denial of service, or possibly execute arbitrary code. (CVE-2019-20218)

It was discovered that SQLite incorrectly handled generated column optimizations. An attacker could use this issue to cause SQLite to crash, resulting in a denial of service, or possibly execute arbitrary code. This issue only affected Ubuntu 18.04 LTS and Ubuntu 19.10. (CVE-2020-9327)