-
-
Notifications
You must be signed in to change notification settings - Fork 116
SQLite 3.30.1 #323
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Will do. |
Hi Eric, Any update on the SQlite 3.30.1? |
I can assure you that when there is an update, it will be visible here in this issue. I haven't gotten this done yet. Soon. |
I assume you are talking about the so-called "Magellan 2.0" stuff from Tencent. FWIW, the author of SQLite posted something on the sqlite-users mailing list yesterday giving his opinion about the urgency (or lack of same) on this issue. Anyway, regardless of whether these vulnerabilities are urgent or not, as far as I can tell, 3.30.1 does not actually contain a patch for them. |
According to https://nvd.nist.gov/vuln/detail/CVE-2019-19646 |
I'm not interested in arguing about how critical this is or is not. The fact remains, there is AFAICT no SQLite release which contains a fix. |
No arguing here. I missed the fact that 3.30.1 was also affected |
I'm eager to use the following features:
|
In progress at #340 |
v2.0.3 has been pushed to nuget. Its e_sqlite3 bulds are at 3.31.1. |
It seems like sqlcipher is still 4.2.0 (based on sqlite 3.28.0). |
Yes, probably. (The e_sqlcipher builds are unofficial and unsupported, and I update them less frequently. I typically recommend that folks buy official builds from Zetetic. ) |
@ericsink |
Currently used version of SQLite has a known vulnerability. Could you please upgrade SQLite to version above 3.30.1?
The text was updated successfully, but these errors were encountered: