Show filters
48 Total Results
Displaying 41-48 of 48
Sort by:
Attacker Value
Unknown
CVE-2020-13632
Disclosure Date: May 27, 2020 (last updated February 21, 2025)
ext/fts3/fts3_snippet.c in SQLite before 3.32.0 has a NULL pointer dereference via a crafted matchinfo() query.
0
Attacker Value
Unknown
CVE-2020-13434
Disclosure Date: May 24, 2020 (last updated February 21, 2025)
SQLite through 3.32.0 has an integer overflow in sqlite3_str_vappendf in printf.c.
0
Attacker Value
Unknown
CVE-2020-11656
Disclosure Date: April 09, 2020 (last updated February 21, 2025)
In SQLite through 3.31.1, the ALTER TABLE implementation has a use-after-free, as demonstrated by an ORDER BY clause that belongs to a compound SELECT statement.
0
Attacker Value
Unknown
CVE-2020-11655
Disclosure Date: April 09, 2020 (last updated February 21, 2025)
SQLite through 3.31.1 allows attackers to cause a denial of service (segmentation fault) via a malformed window-function query because the AggInfo object's initialization is mishandled.
0
Attacker Value
Unknown
CVE-2020-9327
Disclosure Date: February 21, 2020 (last updated February 21, 2025)
In SQLite 3.31.1, isAuxiliaryVtabOperator allows attackers to trigger a NULL pointer dereference and segmentation fault because of generated column optimizations.
0
Attacker Value
Unknown
CVE-2020-6851
Disclosure Date: January 13, 2020 (last updated February 21, 2025)
OpenJPEG through 2.3.1 has a heap-based buffer overflow in opj_t1_clbl_decode_processor in openjp2/t1.c because of lack of opj_j2k_update_image_dimensions validation.
0
Attacker Value
Unknown
CVE-2019-12973
Disclosure Date: June 26, 2019 (last updated November 27, 2024)
In OpenJPEG 2.3.1, there is excessive iteration in the opj_t1_encode_cblks function of openjp2/t1.c. Remote attackers could leverage this vulnerability to cause a denial of service via a crafted bmp file. This issue is similar to CVE-2018-6616.
0
Attacker Value
Unknown
CVE-2018-20843
Disclosure Date: June 24, 2019 (last updated November 08, 2023)
In libexpat in Expat before 2.2.7, XML input including XML names that contain a large number of colons could make the XML parser consume a high amount of RAM and CPU resources while processing (enough to be usable for denial-of-service attacks).
0