Skip to content
COOEY

FAIL › dossier

ontap select deploy administration utility

PRODUCT

Dossier not yet built — the RAG curator builds one for players with ≥2 failure events. The failure history and sentiment below are live.
FAILURE HISTORY · 14
DATEEVENTSEVSUMMARY
2022-09-01 CVE-2020-35527 critical CVE-2020-35527: In SQLite 3.31.1, there is an out of bounds access problem through ALTER TABLE f
2022-08-05 CVE-2022-37434 critical CVE-2022-37434: zlib through 1.2.12 has a heap-based buffer over-read or buffer overflow in infl
2021-07-22 CVE-2021-35942 critical CVE-2021-35942: The wordexp function in the GNU C Library (aka glibc) through 2.33 may crash or
2021-06-02 CVE-2021-3520 critical CVE-2021-3520: There's a flaw in lz4. An attacker who submits a crafted file to an application
2021-01-19 CVE-2021-3177 critical CVE-2021-3177: Python 3.x through 3.9.1 has a buffer overflow in PyCArg_repr in _ctypes/callpro
2020-04-09 CVE-2020-11656 critical CVE-2020-11656: In SQLite through 3.31.1, the ALTER TABLE implementation has a use-after-free, a
2019-12-09 CVE-2019-19646 critical CVE-2019-19646: pragma.c in SQLite through 3.30.1 mishandles NOT NULL in an integrity_check PRAG
2019-12-05 CVE-2019-19317 critical CVE-2019-19317: lookupName in resolve.c in SQLite 3.30.1 omits bits from the colUsed bitmask in
2019-03-25 CVE-2019-3860 medium CVE-2019-3860: An out of bounds read flaw was discovered in libssh2 before 1.8.1 in the way SFT
2019-03-25 CVE-2019-3861 medium CVE-2019-3861: An out of bounds read flaw was discovered in libssh2 before 1.8.1 in the way SSH
2019-03-21 CVE-2019-3859 critical CVE-2019-3859: An out of bounds read flaw was discovered in libssh2 before 1.8.1 in the _libssh
2019-03-21 CVE-2019-3858 medium CVE-2019-3858: An out of bounds read flaw was discovered in libssh2 before 1.8.1 when a special
2019-03-21 CVE-2019-3862 high CVE-2019-3862: An out of bounds read flaw was discovered in libssh2 before 1.8.1 in the way SSH
2019-02-26 CVE-2019-9169 critical CVE-2019-9169: In the GNU C Library (aka glibc or libc6) through 2.29, proceed_next_node in pos