LiveActive security incident?Get immediate response
CVE Record

CVE-2019-19317: lookupName in resolve.c in SQLite 3.30.1 omits bits from the colUsed bitmask in the case of a generated col...

lookupName in resolve.c in SQLite 3.30.1 omits bits from the colUsed bitmask in the case of a generated column, which allows attackers to cause a denial of service or possibly have unspecified other impact.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2019-19317 is a SQLite bug in name resolution for generated columns. The public record says it can let an attacker cause denial of service, with possible unspecified other impact. The supplied sources do not provide CVSS, CWE, affected vendor matrix, or confirmed exploitation.

Executive priority

Handle as a dependency risk with incomplete severity data. It does not justify emergency response from the supplied evidence alone, but it should be included in patch governance for products embedding SQLite, especially externally exposed or attacker-input-facing systems.

Technical view

In SQLite 3.30.1, lookupName in resolve.c omits bits from the colUsed bitmask when resolving a generated column. That incorrect column-use tracking is associated with denial of service and possibly other unspecified impact. Upstream SQLite commits are referenced, but the bundle does not name a fixed release.

Likely exposure

Exposure is most likely in applications, appliances, or products embedding vulnerable SQLite code, especially where untrusted database files, SQL, or generated-column schemas can be processed. The bundle names NetApp, Oracle, and Siemens advisories, but does not provide affected product details.

Exploitation context

The source bundle does not indicate active exploitation, and KEV is false. Treat exploitation evidence as unconfirmed. The practical risk depends on whether attackers can influence SQLite inputs in a deployed product or application.

Researcher notes

The key technical clue is incorrect colUsed bitmask handling for generated columns in resolve.c. The record is sparse: no CVSS, no CWE, no precise affected CPEs, and no fixed release in the bundle. Validate impact through version and vendor mapping, not assumptions.

Mitigation direction

  • Inventory products and applications that embed SQLite around version 3.30.1.
  • Review upstream SQLite commits and vendor advisories for fixed versions.
  • Update SQLite or vendor packages using official guidance.
  • Prioritize systems processing untrusted database files or SQL input.
  • Monitor NetApp, Oracle, and Siemens advisories for product-specific remediation.

Validation and detection

  • Confirm the SQLite version embedded in each application or appliance.
  • Check SBOMs and vendor notices for CVE-2019-19317 references.
  • Verify whether generated columns are supported and reachable in exposed workflows.
  • Confirm patched builds include the referenced SQLite source changes.
  • Document products where vendor impact remains unknown.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-19317 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.