Security Advisory

CVE-2019-19646: SQLite integrity_check NOT NULL

Last updated:
  • CVE-2019-19646

CVE-2019-19646 is an improper check for an unusual condition (CWE-754) in SQLite's PRAGMA integrity_check: the NOT NULL test mishandles some generated columns. NVD scores it 9.8, but the SQLite project says the bug can make the statement loop forever, a denial of service, and generated columns first shipped in 3.31.0.

Vulnerability summary

CVSS base score

9.8

Critical severity

EPSS score (FIRST)

7.4%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2019-19646 · Source: NVD

Affected components

ComponentCPEVersion range
SQLitecpe:2.3:a:sqlite:sqlite:*:*:*:*:*:*:*:*through 3.30.1 (NVD); the SQLite project lists the fix in 3.31.0, the first release with generated columns
Siemens SINEC INScpe:2.3:a:siemens:sinec_infrastructure_network_services:*:*:*:*:*:*:*:*before V1.0.1.1 (Siemens SSA-389290)

What does this mean for affected devices?

NVD's description: "pragma.c in SQLite through 3.30.1 mishandles NOT NULL in an integrity_check PRAGMA command in certain cases of generated columns." NVD's Primary score is CVSS v3.1 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and CVSS v2 7.5, with CWE-754. The CPE configuration lists SQLite through 3.30.1 together with Siemens SINEC INS before 1.0.1.1, Tenable.sc, MySQL Workbench and NetApp products, and the record was published on 2019-12-09 (NVD).

What does the bug actually do?

The SQLite Vulnerabilities page lists it as fixed in 3.31.0 (2020-01-22) and says PRAGMA integrity_check "might cause the byte-code for a prepared statement to loop indefinitely", which "might enable a denial-of-service, if the application has not taken appropriate and prudent steps to limit the run-time of SQL statements." It adds that "this is not a vulnerability, as there are countless perfectly valid SQL queries" that run "essentially forever." Nothing in the project's account supports the code execution that a 9.8 score implies; read the score as a CPE-driven worst case.

Is a 3.30.x library really affected?

Probably not. SQLite's generated columns page says support "was added with SQLite version 3.31.0", and the fix landed on 2019-12-09, before that release. The Debian security tracker marks both sqlite3 and the older sqlite package as not affected, noting "Generated column support added later." A scanner that flags 3.30.1 or older for this CVE is matching NVD's version range, not code the library contains. A hit on a pre-release snapshot of 3.31.0 is the one case to check.

Which device products list it?

Siemens lists it for SINEC INS, its infrastructure network services server, in SSA-389290 (2022-03-08), with Siemens' own score of 9.8 and the fix "Update to V1.0.1.1 or later version." Our SQLite firmware guide explains how to read the exact SQLite release from a binary, which settles whether generated-column code is present. The SQLite page notes that most SQLite CVEs need attacker SQL, as do CVE-2018-20346 and CVE-2022-46908; CVE-2022-35737 is the exception.

How do you fix or mitigate it?

Ship SQLite 3.31.0 or later, or the vendor update, such as SINEC INS V1.0.1.1. Where untrusted SQL can reach the library, SQLite's Defense Against the Dark Arts page recommends lower sqlite3_limit() values and a sqlite3_progress_handler() callback or sqlite3_interrupt() timer to bound run time, which covers this loop and every other long-running query.

CVE-2019-19646 is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.07402, the 94.5th percentile, in the 2026-11-17 dataset (CISA KEV, FIRST EPSS).

How to fix this class of issueNo dedicated SoftWSP guide covers this weakness class; the fix is usually the vendor patch or firmware update referenced above. Our related guide explains how to plan and verify it: NIST SP 800-40 Rev. 4: enterprise patch management planning, explained.

Evidence

  • NVD: pragma.c in SQLite through 3.30.1 mishandles NOT NULL in an integrity_check PRAGMA for certain generated columns; Primary CVSS v3.1 9.8, CVSS v2 7.5; CWE-754; CPE sqlite <= 3.30.1, Siemens SINEC INS < 1.0.1.1, Tenable.sc < 5.19.0, MySQL Workbench <= 8.0.19, NetApp; published 2019-12-09. — NVD
  • SQLite Vulnerabilities page: CVE-2019-19646 fixed in 3.31.0 (2020-01-22); PRAGMA integrity_check might loop indefinitely; possible denial of service; "This is not a vulnerability". — SQLite
  • SQLite generated columns: support added with SQLite 3.31.0. — SQLite
  • Debian: sqlite3 and sqlite not affected, "Generated column support added later". — Debian security tracker
  • Siemens SSA-389290 (2022-03-08): SINEC INS affected; Update to V1.0.1.1 or later version; Siemens CVSS 9.8. — Siemens ProductCERT
  • SQLite Defense Against the Dark Arts: reduce limits with sqlite3_limit(); use sqlite3_progress_handler() or sqlite3_interrupt() to bound run time. — SQLite
  • CVE-2019-19646 is not in the CISA KEV catalog, version 2026.11.17 (1,782 entries), checked 2026-11-18. — CISA KEV
  • EPSS 0.07402, percentile 0.94536, dataset 2026-11-17. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. SQLite: Vulnerabilities
  3. SQLite: Generated columns
  4. Debian security tracker
  5. Siemens SSA-389290: SINEC INS
  6. SQLite: Defense Against the Dark Arts
  7. CISA KEV
  8. FIRST EPSS

Frequently asked questions

Why does NVD score CVE-2019-19646 at 9.8?

NVD assigned a network, no-privilege, full-impact vector. The SQLite project describes the bug as PRAGMA integrity_check possibly looping indefinitely, a denial of service at worst, and says it is not a vulnerability in practice (per NVD and the SQLite Vulnerabilities page).

Is SQLite 3.30.1 affected by CVE-2019-19646?

NVD lists versions through 3.30.1, but the bug is in generated-column handling, and SQLite added generated columns in 3.31.0, which shipped with the fix. Debian marks its sqlite3 packages as not affected for that reason (per SQLite and the Debian security tracker).

Which Siemens product is affected by CVE-2019-19646?

Siemens SSA-389290 lists SINEC INS and tells users to update to V1.0.1.1 or later (per Siemens ProductCERT).

Is CVE-2019-19646 in the CISA KEV catalog?

No, not as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.07402, the 94.5th percentile, in the 2026-11-17 dataset (per CISA KEV and FIRST EPSS).