SQLiteDatabase / datastore

CVE-2021-36690

HIGH · 7.5 CVSS v3.1 Published 2021-08-24
Fix available
A fix is available. Upgrade to 9.0 / 13.0 or later.
See remediation →
84/100
Remediation priority · High
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A segmentation fault can occur in the sqlite3.exe command-line component of SQLite 3.36.0 via the idxGetTableInfo function when there is a crafted SQL query. NOTE: the vendor disputes the relevance of this report because a sqlite3.exe user already has full privileges (e.g., is intentionally allowed to execute commands). This report does NOT imply any problem in the SQLite library.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SQLiteDatabase / datastore
Affected:= 3.36.0
Zfs Storage Appliance KitApplication
Affected:= 8.8
Iphone OsOperating system
Affected:< 16.0
macOSOperating system
Affected:< 13.0
TvosOperating system
Affected:< 16.0
WatchosOperating system
Affected:< 9.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.0 / 13.0 / 16.0 or later
Fixed in 9.013.016.0
Vendor patch www.sqlite.org →
Recommended fix Moderate confidence

SQLite 3.37.0+ | iOS 16.0+ | macOS 13.0+ | tvOS 16.0+ | watchOS 9.0+

  1. For SQLite: Upgrade to SQLite version 3.37.0 or later, which contains the fix for the segmentation fault in idxGetTableInfo
  2. For Apple devices: Update to iOS 16.0 or later to address the vulnerability in the SQLite library
  3. For Apple devices: Update to macOS 13.0 or later
  4. For Apple devices: Update to tvOS 16.0 or later
  5. For Apple devices: Update to watchOS 9.0 or later
  6. For Zfs Storage Appliance Kit: Contact Oracle for the specific patched version (8.8 was listed as affected, check for 8.8.1 or later)
Caveat The SQLite vendor disputes the security relevance, noting sqlite3.exe users already have full system privileges; no breaking changes expected for library consumers

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-36690 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-36690 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data