4 ms·
If I understand this correctly, you need a malicious sqlite database file, which I don’t think you could create with sqlite itself. Which means, in order to exp
by hanche 6y ago
If I understand this correctly, you need a malicious sqlite database file, which I don’t think you could create with sqlite itself. Which means, in order to exploit this, you first have to get this malicious database onto their computer. So while this seems serious enough, it may not be time to panic quite yet.
- progval 6y agoI'm guessing this submission is a reaction to another post on the frontpage: "SQLite as an Application File Format" https://news.ycombinator.com/item?id=23508923 https://news.ycombinator.com/item?id=23508923 In this case it's relevant, as untrusted SQLite files would be downloaded and loaded in this context.
- hanche 6y agoI see. I had thought of that more as a format for applications to store their persistent data than for data interchange. When used for the latter, the danger seems clear enough. (I also just noticed that the original post is half a year old.)
- recursivecaveat 6y agoIf you're using it for persistent storage, its probably inevitable that a user sends in their copy as part of a bug report and a developer cracks it open.
- hanche 6y agoGood point.
- dathinab 6y agoTrue but even as a interchange file format sqlite is interesting. Through you probably want some hardened against this types of attacks form of sqlite. Like one which had just a subset of features and sqlsupport.
- ifdefdebug 6y agoIn this case you should run integrity check (sqlite built in) then schema check (app specific) first thing after open.