CVE-2020-13630: ext/fts3/fts3.c in SQLite before 3.32.0 has a use-after-free in fts3EvalNextRow, related to the snippet feature.
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 63.9% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: mingw-binutils-generic (AlmaLinux:8) 2.30-3.el8; mingw-filesystem-base (AlmaLinux:8) 104-2.el8; mingw32-binutils (AlmaLinux:8) 2.30-3.el8.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to mingw-binutils-generic (AlmaLinux:8) 2.30-3.el8; mingw-filesystem-base (AlmaLinux:8) 104-2.el8; mingw32-binutils (AlmaLinux:8) 2.30-3.el8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
- Published
- May 27, 2020
- Updated
- Oct 14, 2026
- EPSS
- 1.0% · 63th percentile
- CWE
- CWE-416
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| sqlite | sqlite | cpe:2.3:a:sqlite:sqlite |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| netapp | cloud backup | cpe:2.3:a:netapp:cloud_backup |
| netapp | solidfire, enterprise sds & hci storage node | cpe:2.3:a:netapp:solidfire,_enterprise_sds_&_hci_storage_node |
| broadcom | fabric operating system | cpe:2.3:o:broadcom:fabric_operating_system |
| netapp | hci compute node firmware | cpe:2.3:o:netapp:hci_compute_node_firmware |
| netapp | hci compute node | cpe:2.3:h:netapp:hci_compute_node |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| siemens | sinec infrastructure network services | cpe:2.3:a:siemens:sinec_infrastructure_network_services |
| apple | icloud | cpe:2.3:a:apple:icloud |
| apple | itunes | cpe:2.3:a:apple:itunes |
and 8 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apple icloudbefore 11.5
- apple ipadosbefore 14.0
- apple iphone osbefore 14.0
- apple itunesbefore 12.10.9
- apple macosbefore 11.0.1
- apple tvosbefore 14.0
- apple watchosbefore 7.0
- broadcom fabric operating systemall versions
+12 more rows
- canonical ubuntu linux16.04
- canonical ubuntu linux18.04
- canonical ubuntu linux19.10
- canonical ubuntu linux20.04
- debian debian linux9.0
- fedoraproject fedora32
- netapp cloud backupall versions
- netapp hci compute node firmwareall versions
- netapp solidfire, enterprise sds & hci storage nodeall versions
- oracle communications network charging and control12.0.0 and later · up to 12.0.3 inclusive
- oracle communications network charging and control6.0.1
- oracle outside in technology8.5.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | mingw-binutils-generic | before 2.30-3.el8 | 2.30-3.el8 |
| AlmaLinux:8 | mingw-filesystem-base | before 104-2.el8 | 104-2.el8 |
| AlmaLinux:8 | mingw32-binutils | before 2.30-3.el8 | 2.30-3.el8 |
| AlmaLinux:8 | mingw32-bzip2 | before 1.0.6-14.el8 | 1.0.6-14.el8 |
| AlmaLinux:8 | mingw32-bzip2-static | before 1.0.6-14.el8 | 1.0.6-14.el8 |
| AlmaLinux:8 | mingw32-filesystem | before 104-2.el8 | 104-2.el8 |
| AlmaLinux:8 | mingw32-sqlite | before 3.26.0.0-1.el8 | 3.26.0.0-1.el8 |
| AlmaLinux:8 | mingw32-sqlite-static | before 3.26.0.0-1.el8 | 3.26.0.0-1.el8 |
| AlmaLinux:8 | mingw64-binutils | before 2.30-3.el8 | 2.30-3.el8 |
| AlmaLinux:8 | mingw64-bzip2 | before 1.0.6-14.el8 | 1.0.6-14.el8 |
| AlmaLinux:8 | mingw64-bzip2-static | before 1.0.6-14.el8 | 1.0.6-14.el8 |
| AlmaLinux:8 | mingw64-filesystem | before 104-2.el8 | 104-2.el8 |
| AlmaLinux:8 | mingw64-sqlite | before 3.26.0.0-1.el8 | 3.26.0.0-1.el8 |
| AlmaLinux:8 | mingw64-sqlite-static | before 3.26.0.0-1.el8 | 3.26.0.0-1.el8 |
| Debian:12 | sqlite3 | before 3.32.0-1 | 3.32.0-1 |
| Debian:9 | sqlite3 | before 3.16.2-5+deb9u2 | 3.16.2-5+deb9u2 |
| openSUSE:Leap 15.2 | sqlite3 | before 3.36.0-lp152.4.3.1 | 3.36.0-lp152.4.3.1 |
| openSUSE:Leap 15.3 | sqlite3 | before 3.36.0-3.12.1 | 3.36.0-3.12.1 |
| openSUSE:Tumbleweed | sqlite3 | before 3.36.0-1.2 | 3.36.0-1.2 |
| Red Hat:enterprise_linux:8::appstream | lemon | before 0:3.26.0-11.el8 | 0:3.26.0-11.el8 |
| Red Hat:enterprise_linux:8::appstream | lemon-debuginfo | before 0:3.26.0-11.el8 | 0:3.26.0-11.el8 |
| Red Hat:enterprise_linux:8::appstream | sqlite-analyzer-debuginfo | before 0:3.26.0-11.el8 | 0:3.26.0-11.el8 |
| Red Hat:enterprise_linux:8::appstream | sqlite-debuginfo | before 0:3.26.0-11.el8 | 0:3.26.0-11.el8 |
| Red Hat:enterprise_linux:8::appstream | sqlite-debugsource | before 0:3.26.0-11.el8 | 0:3.26.0-11.el8 |
+37
Same product
sqlite: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-8457SQLite3 from 3.6.0 to and including 3.27.2 is vulnerable to heap out-of-bound read in the rtreenode() function when handling invalid rtree…53Plan
- CVE-2025-6965Integer Truncation on SQLite50Plan
- CVE-2015-5895Multiple unspecified vulnerabilities in SQLite before 3.8.10.2, as used in Apple iOS before 9, have unknown impact and attack vectors.43Plan
Published before and after this one in the same product
- ← EarlierCVE-2020-13434May 24, 2020 · SQLite through 3.32.0 has an integer overflow in sqlite3_str_vappendf in printf.c.22Monitor
- ← EarlierCVE-2020-13435May 24, 2020 · SQLite through 3.32.0 has a segmentation fault in sqlite3ExprCodeTarget in expr.c.22Monitor
- Later →CVE-2020-13631May 27, 2020 · SQLite before 3.32.0 allows a virtual table to be renamed to the name of one of its shadow tables, related to alter.c and build.c.22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:mingw-binutils-generic | 2.30-3.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:mingw-filesystem-base | 104-2.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:mingw32-binutils | 2.30-3.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:mingw32-bzip2 | 1.0.6-14.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:mingw32-bzip2-static | 1.0.6-14.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:mingw32-filesystem | 104-2.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:mingw32-sqlite | 3.26.0.0-1.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:mingw32-sqlite-static | 3.26.0.0-1.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:mingw64-binutils | 2.30-3.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:mingw64-bzip2 | 1.0.6-14.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:mingw64-bzip2-static | 1.0.6-14.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:mingw64-filesystem | 104-2.el8 · AlmaLinux:8 | Package registry (OSV) |
| debian:sqlite3 | 3.32.0-1 · Debian:12 | Package registry (OSV) |
| opensuse:sqlite3 | 3.36.0-lp152.4.3.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| red hat:lemon | 0:3.26.0-11.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:lemon-debuginfo | 0:3.26.0-11.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:mingw-binutils | 0:2.30-3.el8 · Red Hat:enterprise_linux:8::crb | Package registry (OSV) |
| red hat:sqlite | 0:3.26.0-11.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:sqlite-analyzer-debuginfo | 0:3.26.0-11.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:sqlite-debuginfo | 0:3.26.0-11.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:sqlite-debugsource | 0:3.26.0-11.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:sqlite-devel | 0:3.26.0-11.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:sqlite-doc | 0:3.26.0-11.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:sqlite-libs | 0:3.26.0-11.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:sqlite-libs-debuginfo | 0:3.26.0-11.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:sqlite-tcl-debuginfo | 0:3.26.0-11.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| rocky linux:mingw-binutils | 0:2.30-3.el8 · Rocky Linux:8 | Package registry (OSV) |
| rocky linux:mingw-bzip2 | 0:1.0.6-14.el8 · Rocky Linux:8 | Package registry (OSV) |
| rocky linux:mingw-sqlite | 0:3.26.0.0-1.el8 · Rocky Linux:8 | Package registry (OSV) |
| suse:sqlite3 | 3.36.0-3.12.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-22-0215 · Mar 11, 2022(Siemens Güvenlik Bildirimi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- seclists.org/fulldisclosure/2020/Nov/19
- seclists.org/fulldisclosure/2020/Nov/20
- seclists.org/fulldisclosure/2020/Nov/22
- bugs.chromium.org/p/chromium/issues/detail?id=1080459
- cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf
- lists.debian.org/debian-lts-announce/2020/08/msg00037.html
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/L7KXQWHIY2MQP4LNM6ODWJENMXYYQYBN/
- security.FreeBSD.org/advisories/FreeBSD-SA-20:22.sqlite.asc
- security.gentoo.org/glsa/202007-26
- security.netapp.com/advisory/ntap-20200608-0002/
- sqlite.org/src/info/0d69f76f0865f962
- support.apple.com/kb/HT211843
- support.apple.com/kb/HT211844
- support.apple.com/kb/HT211850
- support.apple.com/kb/HT211931
- support.apple.com/kb/HT211935
- support.apple.com/kb/HT211952
- usn.ubuntu.com/4394-1/
- www.oracle.com/security-alerts/cpujul2020.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.