Can you elaborate about this? What are the gotchas when opening an untrusted SQLite3 database?
(I am developing a web application that will allow users to upload application files, which are SQLite3 databases)
(I am developing a web application that will allow users to upload application files, which are SQLite3 databases)
If you stick with the core, and disable some of the shiny features, the track record is better. Though still not spotless, iirc.
See https://www.cvedetails.com/vulnerability-list/vendor_id-9237...
Hundreds of thousands of lines of code are simply going to have vulnerabilities and bugs. It's unavoidable with that level of complexity. I'm skeptical anything that complicated is a wise choice for a general file format -- especially when smaller, simpler, and more easily debuggable and independently implementable formats exist.