CVE-2020-35525

In SQlite 3.31.1, a potential null pointer derreference was found in the INTERSEC query processing.

Published: 2022-09-01 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-35525 is rated Moderate Risk (49.8/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.89%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2020-35525

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.23% 0.89% +0.66%
2 2025-11-21 0.33% 0.23% -0.10%
3 2025-11-18 — 0.33% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-35525

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2020-35525

OS Trackers for CVE-2020-35525

vendor priority summary link
debian not yet assigned CVE-2020-35525 not yet assigned priority: Debian including 1 source packages (sqlite3), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2020-35525
redhat low — https://access.redhat.com/security/cve/CVE-2020-35525
suse medium CVE-2020-35525 severity moderate: SUSE including 11 source package names (lemon-3.26.0-16.el8_6, libsqlite3-0, …), 139 product×package rows across 41 product lines (SUSE CaaS Platform 4.0, SUSE Enterprise Storage 6, … (41 product lines)): Known Not Affected 133, Fixed 5, Will Not Fix 1. https://www.suse.com/security/cve/CVE-2020-35525/
ubuntu medium CVE-2020-35525 medium priority: Ubuntu including 2 source packages (sqlite, sqlite3), 22 status rows across 11 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, trusty, upstream, xenial): not-affected 11, released 6, DNE 4, ignored 1. https://ubuntu.com/security/CVE-2020-35525

Affected software / configurations for CVE-2020-35525

Vendor Product Version Raw CPE
sqlite sqlite 3.31.1 cpe:2.3:a:sqlite:sqlite:3.31.1:*:*:*:*:*:*:*

References for CVE-2020-35525

cvelogic Threat Intelligence