SQL Injection in SQLCipher Export Function
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Zetetic | SQLCipher | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Zetetic | Sqlcipher |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.180% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | SQL Injection in SQLCipher Export Function |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Zetetic SQLCipher before 4.15.0 allows SQL injection. The sqlcipher_export convenience function can be used to copy the contents of one attached database into another. It is most often used to convert between plaintext and encrypted databases. It needs to do dynamic schema manipulation, and thus the function temporarily clears defensive restrictions during operation. A vulnerability in the handling of the source database name parameter made it possible for a caller to supply a crafted source name, which could execute statements that defensive mode would otherwise block. This could allow direct modifications to the sqlite_schema table and database corruption. SQLCipher 4.15.0 now strictly validates the source database name and prevents the bypass. | |
| First Time appeared |
Zetetic
Zetetic sqlcipher |
|
| Weaknesses | CWE-89 | |
| CPEs | cpe:2.3:a:zetetic:sqlcipher:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Zetetic
Zetetic sqlcipher |
|
| References |
| |
| Metrics |
cvssV4_0
|