SQLite 3.30.1 Update ext/misc/zipfile.c zipfileUpdate ZIP Archive unrestricted upload
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in SQLite 3.30.1. This issue affects the function zipfileUpdate of the file ext/misc/zipfile.c of the component Update Handler. The manipulation as part of ZIP Archive leads to unrestricted upload.
This vulnerability is documented as CVE-2019-19925. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability, which was classified as critical, has been found in SQLite 3.30.1. This issue affects the function zipfileUpdate of the file ext/misc/zipfile.c of the component Update Handler. The manipulation as part of a ZIP Archive leads to a unrestricted upload vulnerability. Using CWE to declare the problem leads to CWE-434. The product allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment. Impacted is availability. The summary by CVE is:
zipfileUpdate in ext/misc/zipfile.c in SQLite 3.30.1 mishandles a NULL pathname during an update of a ZIP archive.
The weakness was released 12/24/2019. The identification of this vulnerability is CVE-2019-19925 since 12/23/2019. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1608.002 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 236583 (Alibaba Cloud Linux 3 : 0111: sqlite (ALINUX3-SA-2022:0111)), which helps to determine the existence of the flaw in a target environment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Tenable (236583). Entries connected to this vulnerability are available at VDB-147700 and VDB-147699. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
Website
- Product: https://github.com/sqlite/sqlite/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.5
VulDB Temp Score: 7.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Unrestricted uploadCWE: CWE-434 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 236583
Nessus Name: Alibaba Cloud Linux 3 : 0111: sqlite (ALINUX3-SA-2022:0111)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
12/23/2019 🔍12/24/2019 🔍
12/25/2019 🔍
05/21/2025 🔍
Sources
Product: github.comAdvisory: RHSA-2020:0514
Status: Confirmed
CVE: CVE-2019-19925 (🔍)
GCVE (CVE): GCVE-0-2019-19925
GCVE (VulDB): GCVE-100-147701
See also: 🔍
Entry
Created: 12/25/2019 10:00Updated: 05/21/2025 12:33
Changes: 12/25/2019 10:00 (40), 12/25/2019 10:05 (17), 03/16/2024 18:03 (5), 05/21/2025 12:33 (23)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.