LiveActive security incident?Get immediate response
CVE Record

CVE-2022-35737: SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bounds overflow if billions of bytes a...

SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bounds overflow if billions of bytes are used in a string argument to a C API.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

SQLite versions before 3.39.2 can fail unsafely when an application passes extremely large string data into a SQLite C API. The practical risk is highest where attackers can make a service process unusually large inputs that reach SQLite. The published scoring emphasizes denial of service, not confirmed data theft or active exploitation.

Executive priority

Treat as a high-priority dependency update where SQLite is exposed through public services or embedded products. It is less urgent than a confirmed exploited remote-code issue, but broad SQLite use makes inventory important.

Technical view

CVE-2022-35737 is an array-bounds overflow in SQLite 1.0.12 through 3.39.x before 3.39.2, triggered by billions of bytes in a string argument to a C API. SQLite 3.39.2 includes the fix. Sources also show downstream vendor and distribution advisories, indicating embedded dependency exposure matters.

Likely exposure

Exposure is likely in applications, appliances, or distributions bundling affected SQLite versions, especially statically linked copies. Risk depends on whether untrusted input can become very large string arguments to SQLite's C API.

Exploitation context

The provided bundle does not show CISA KEV listing or cited evidence of active exploitation. The condition requires extremely large string inputs, which may limit exploitability but can still threaten service availability.

Researcher notes

Focus validation on version provenance and reachability. The core precondition is attacker-influenced, extremely large string data reaching SQLite C API usage. Do not assume exposure solely from having SQLite installed.

Mitigation direction

  • Upgrade SQLite to 3.39.2 or later.
  • Apply operating system, distribution, and vendor appliance updates.
  • Check vendor advisories for embedded SQLite dependencies.
  • Prioritize internet-facing services handling untrusted large inputs.
  • Restart or redeploy services after library replacement.

Validation and detection

  • Inventory SQLite versions from packages, containers, and SBOMs.
  • Identify statically linked or vendored SQLite copies.
  • Confirm runtime libraries report 3.39.2 or later.
  • Map untrusted input paths reaching SQLite C APIs.
  • Review NetApp, Gentoo, and vendor-specific advisory status.
Prepared
Confidence
high
Sources
8

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-2022-35737 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

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.

1CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2022-35737Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
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.