News for hackers. Stuff that matters.
Re:Select Code_execution from * Using SQLite; (2019) by thunderbong on Saturday June 13, 2020 @11:02PM (#23514757)
>> We created a rogue SQLite database that exploits the software used to open it.

So, here, they are replacing the whole database and then stealing the passwords? I would guess that if a malicious actor has that kind of access to the system, all is lost.

Re:Select Code_execution from * Using SQLite; (2019) by XMPPwocky on Saturday June 13, 2020 @11:13PM (#23514795)
SQLite notably is often used as a file format. For example, for browser cookie storage.

As you can see in the next sentence after your quote,

> Exploring only a few of the possibilities this presents we’ll pwn password stealer backends while they parse credentials files and achieve iOS persistency by replacing its Contacts database…

(The major browsers store passwords in SQLite databases, so password stealers upload those to a backend. iOS makes it hard to run code persistently (if you have a shell once, can you keep it after a reboot), so the Contacts database is a target for persistence.)