CVE-2020-13434 — SQLite through 3.32.0 has an integer overflow in sqlite3_str_vappendf in printf.c.
SQLite through 3.32.0 has an integer overflow in sqlite3_str_vappendf in printf.c.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 1% (30-day exploitation probability)+9
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — www.oracle.com (NIST National Vulnerability Database)
- Documented patch — www.oracle.com (NIST National Vulnerability Database)
- Documented patch — www.oracle.com (NIST National Vulnerability Database)
- Documented patch — www.sqlite.org (NIST National Vulnerability Database)
- Documented patch — www.sqlite.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Apple Icloud, Apple Ipados, Apple Iphone Os…).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Apple | Icloud | < 11.5 | Vulnerable | NIST National Vulnerability Database |
| Apple | Ipados | < 14.0 | Vulnerable | NIST National Vulnerability Database |
| Apple | Iphone Os | < 14.0 | Vulnerable | NIST National Vulnerability Database |
| Apple | Itunes | < 12.10.9 | Vulnerable | NIST National Vulnerability Database |
| Apple | Macos | ≥ 11.0 and < 11.0.1 | Vulnerable | NIST National Vulnerability Database |
| Apple | Tvos | < 14.0 | Vulnerable | NIST National Vulnerability Database |
| Apple | Watchos | < 7.0 | Vulnerable | NIST National Vulnerability Database |
| Canonical | Ubuntu Linux | version 16.04version 18.04version 19.10version 20.04 | Vulnerable | NIST National Vulnerability Database |
| Debian | Debian Linux | version 8.0version 9.0 | Vulnerable | NIST National Vulnerability Database |
| Fedoraproject | Fedora | version 32 | Vulnerable | NIST National Vulnerability Database |
| Freebsd | Freebsd |
version 12.0-p5version 12.0version 12.0-p6version 12.0-p7version 12.0-p8version 12.0-p9version 12.1version 12.1-p1 and 16 moreversion 12.1-p2version 12.1-p3version 12.1-p4version 12.1-p5version 12.1-p6version 12.1-p7version 12.0-p4version 12.0-p3version 12.0-p2version 12.0-p12version 12.0-p11version 12.0-p10version 12.0-p1version 11.4-p1version 11.4≥ 11.0 and < 11.4 |
Vulnerable | NIST National Vulnerability Database |
| Oracle | Communications Cloud Native Core Policy | version 1.14.0 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Communications Network Charging And Control | version 6.0.1≥ 12.0.0 and ≤ 12.0.3 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Outside In Technology | version 8.5.5 | Vulnerable | NIST National Vulnerability Database |
| Sqlite | Sqlite | ≤ 3.32.0 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
| 5.5 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
| 2.1 | CVSS 2.0 | Low | 3.9 | 2.9 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 1.01%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Fix documented
- Affected products added · sqlite/sqlite, debian/debian linux, fedoraproject/fedora, canonical/ubuntu linux, freebsd/freebsd, oracle/communications
- CVSS changed · 5.5
- Source status changed · → Modified
- Record created in this database
- 2020
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
29 on the record
- www.sqlite.org/src/info/d08d3405878d394e
- www.sqlite.org/src/info/23439ea582241138
- www.oracle.com/security-alerts/cpuapr2022.html
- www.oracle.com/security-alerts/cpuApr2021.html
- www.oracle.com/security-alerts/cpujul2020.html
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/L7KX
- lists.debian.org/debian-lts-announce/2020/05/msg00024.html
- seclists.org/fulldisclosure/2020/Nov/20
- security.FreeBSD.org/advisories/FreeBSD-SA-20:22.sqlite.asc
- lists.debian.org/debian-lts-announce/2020/08/msg00037.html
- security.netapp.com/advisory/ntap-20200528-0004
- usn.ubuntu.com/4394-1/
- support.apple.com/kb/HT211844
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/L7KXQW
- security.netapp.com/advisory/ntap-20200528-0004/
- seclists.org/fulldisclosure/2020/Dec/32
- security.gentoo.org/glsa/202007-26
- support.apple.com/kb/HT211843
- support.apple.com/kb/HT211850
- seclists.org/fulldisclosure/2020/Nov/22
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/L7KX
- usn.ubuntu.com/4394-1
- support.apple.com/kb/HT211931
- cert-portal.siemens.com/productcert/html/ssa-398330.html
- nvd.nist.gov/vuln/detail/CVE-2020-13434
- github.com/advisories/GHSA-fjp7-rxx4-gq9h
- seclists.org/fulldisclosure/2020/Nov/19
- support.apple.com/kb/HT211952
- support.apple.com/kb/HT211935
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-101311 Multiple vulnerabilities in bhyve device models 18h
- High CVE-2026-101309 Multiple vulnerabilities in bhyve device models 18h
- High CVE-2026-101310 Multiple vulnerabilities in bhyve device models 18h
- Unknown CVE-2026-58100 Memory safety bugs in kqueue copy-on-fork implementation 19h
- Unknown CVE-2026-58098 Heap out-of-bounds access in semop(2) 19h
- Unknown CVE-2026-58099 Memory safety bugs in kqueue copy-on-fork implementation 19h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2020-13434 is "SQLite through 3.32.0 has an integer overflow in sqlite3_str_vappendf in printf.c.", rated Medium. It affects Icloud (Apple); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 1.01% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.