rpm package
almalinux/mingw-filesystem-base
pkg:rpm/almalinux/mingw-filesystem-base
Vulnerabilities (5)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2020-13630 | — | < 104-2.el8 | 104-2.el8 | May 27, 2020 | ext/fts3/fts3.c in SQLite before 3.32.0 has a use-after-free in fts3EvalNextRow, related to the snippet feature. | ||
| CVE-2020-13631 | — | < 104-2.el8 | 104-2.el8 | May 27, 2020 | SQLite before 3.32.0 allows a virtual table to be renamed to the name of one of its shadow tables, related to alter.c and build.c. | ||
| CVE-2020-13632 | — | < 104-2.el8 | 104-2.el8 | May 27, 2020 | ext/fts3/fts3_snippet.c in SQLite before 3.32.0 has a NULL pointer dereference via a crafted matchinfo() query. | ||
| CVE-2020-13434 | — | < 104-2.el8 | 104-2.el8 | May 24, 2020 | SQLite through 3.32.0 has an integer overflow in sqlite3_str_vappendf in printf.c. | ||
| CVE-2019-16168 | Med | 6.5 | < 104-2.el8 | 104-2.el8 | Sep 9, 2019 | In SQLite through 3.29.0, whereLoopAddBtreeIndex in sqlite3.c can crash a browser or other application because of missing validation of a sqlite_stat1 sz field, aka a "severe division by zero in the query planner." |
- CVE-2020-13630May 27, 2020affected < 104-2.el8fixed 104-2.el8
ext/fts3/fts3.c in SQLite before 3.32.0 has a use-after-free in fts3EvalNextRow, related to the snippet feature.
- CVE-2020-13631May 27, 2020affected < 104-2.el8fixed 104-2.el8
SQLite before 3.32.0 allows a virtual table to be renamed to the name of one of its shadow tables, related to alter.c and build.c.
- CVE-2020-13632May 27, 2020affected < 104-2.el8fixed 104-2.el8
ext/fts3/fts3_snippet.c in SQLite before 3.32.0 has a NULL pointer dereference via a crafted matchinfo() query.
- CVE-2020-13434May 24, 2020affected < 104-2.el8fixed 104-2.el8
SQLite through 3.32.0 has an integer overflow in sqlite3_str_vappendf in printf.c.
- affected < 104-2.el8fixed 104-2.el8
In SQLite through 3.29.0, whereLoopAddBtreeIndex in sqlite3.c can crash a browser or other application because of missing validation of a sqlite_stat1 sz field, aka a "severe division by zero in the query planner."