ext/misc/zipfile.c in SQLite 3.30.1 mishandles certain uses of INSERT INTO in situations involving embedded '\0' characters in filenames, le
Noroxi assessment
Priority: Monitor (action score 31/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: 3.4% (FIRST EPSS); higher than 88.7% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: sqlite3 (Debian:12) 3.30.1+fossil191229-1; sqlite3 (openSUSE:Leap 15.2) 3.36.0-lp152.4.3.1; sqlite3 (openSUSE:Leap 15.3) 3.36.0-3.12.1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to sqlite3 (Debian:12) 3.30.1+fossil191229-1; sqlite3 (openSUSE:Leap 15.2) 3.36.0-lp152.4.3.1; sqlite3 (openSUSE:Leap 15.3) 3.36.0-3.12.1 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
ext/misc/zipfile.c in SQLite 3.30.1 mishandles certain uses of INSERT INTO in situations involving embedded '\0' characters in filenames, leading to a memory-management error that can be detected by (for example) valgrind.
- Published
- Jan 3, 2020
- Updated
- Oct 14, 2026
- EPSS
- 3.4% · 88th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.4%
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux16.04
- canonical ubuntu linux18.04
- canonical ubuntu linux19.10
- sqlite sqlite3.30.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | sqlite3 | before 3.30.1+fossil191229-1 | 3.30.1+fossil191229-1 |
| 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 |
| Red Hat:enterprise_linux:8::appstream | lemon | before 0:3.26.0-6.el8 | 0:3.26.0-6.el8 |
| Red Hat:enterprise_linux:8::appstream | lemon-debuginfo | before 0:3.26.0-6.el8 | 0:3.26.0-6.el8 |
| Red Hat:enterprise_linux:8::appstream | sqlite-analyzer-debuginfo | before 0:3.26.0-6.el8 | 0:3.26.0-6.el8 |
| Red Hat:enterprise_linux:8::appstream | sqlite-debuginfo | before 0:3.26.0-6.el8 | 0:3.26.0-6.el8 |
| Red Hat:enterprise_linux:8::appstream | sqlite-debugsource | before 0:3.26.0-6.el8 | 0:3.26.0-6.el8 |
| Red Hat:enterprise_linux:8::appstream | sqlite-libs-debuginfo | before 0:3.26.0-6.el8 | 0:3.26.0-6.el8 |
| Red Hat:enterprise_linux:8::appstream | sqlite-tcl-debuginfo | before 0:3.26.0-6.el8 | 0:3.26.0-6.el8 |
| Red Hat:enterprise_linux:8::baseos | sqlite | before 0:3.26.0-6.el8 | 0:3.26.0-6.el8 |
| Red Hat:enterprise_linux:8::baseos | sqlite-devel | before 0:3.26.0-6.el8 | 0:3.26.0-6.el8 |
| Red Hat:enterprise_linux:8::baseos | sqlite-doc | before 0:3.26.0-6.el8 | 0:3.26.0-6.el8 |
| Red Hat:enterprise_linux:8::baseos | sqlite-libs | before 0:3.26.0-6.el8 | 0:3.26.0-6.el8 |
| SUSE:HPE Helion OpenStack 8 | sqlite3 | before 3.36.0-9.18.1 | 3.36.0-9.18.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP2 | sqlite3 | before 3.36.0-3.12.1 | 3.36.0-3.12.1 |
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 t53Plan
- 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-2019-19925Dec 24, 2019 · zipfileUpdate in ext/misc/zipfile.c in SQLite 3.30.1 mishandles a NULL pathname during an update of a ZIP archive.32Monitor
- ← EarlierCVE-2019-20218Jan 2, 2020 · selectExpander in select.c in SQLite 3.30.1 proceeds with WITH stack unwinding even after a parsing error.31Monitor
- Later →CVE-2020-9327Feb 21, 2020 · In SQLite 3.31.1, isAuxiliaryVtabOperator allows attackers to trigger a NULL pointer dereference and segmentation fault because of generated31Monitor
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 |
|---|---|---|
| debian:sqlite3 | 3.30.1+fossil191229-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-6.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:lemon-debuginfo | 0:3.26.0-6.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:sqlite | 0:3.26.0-6.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:sqlite-analyzer-debuginfo | 0:3.26.0-6.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:sqlite-debuginfo | 0:3.26.0-6.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:sqlite-debugsource | 0:3.26.0-6.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:sqlite-devel | 0:3.26.0-6.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:sqlite-doc | 0:3.26.0-6.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:sqlite-libs | 0:3.26.0-6.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:sqlite-libs-debuginfo | 0:3.26.0-6.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:sqlite-tcl-debuginfo | 0:3.26.0-6.el8 · Red Hat:enterprise_linux:8::appstream | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-905 · Oct 30, 2020(OpenShift Güvenlik Güncellemesi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.