Numerous applications employing the famous SQLite Database Management System could be revealed to threats due to a possibly critical bug that can lead to distant code implementation, information revelation, and Denial of Service threats. The bug was identified by analysts of the Blade Team based at China-based internet giant Tencent. The professionals have titled the bug “Magellan” and they demand it impacts any piece of software that employs Chromium or SQLite – Chromium believes on WebSQL, which is rooted on SQLite.
SQLite has been one of the most famous database systems and it has presented in a important quantity of web application frameworks, operating systems, web browsers, and different applications created by tech giants likely Microsoft and Adobe. Additionally to Google Chrome, the open source web browser project Slimjet Browser, Chromium powers Opera, Yandex Browser, Torch, Comodo Dragon, SRWare Iron, Vivaldi, and CoolNovo.
The bug can be employed distantly by acquiring the marked user to access a particularly crafted web page according to Tencent Blade analysts. Tencent Blade states it has not been announcing any data or exploit code, however demands to have successfully proven it against a Google Home device. The bug has been fixed by SQLite developers with the announce of version 3.26.0 on December 1. It has also been stated in Chromium and in Chrome (on December 4 with the announcement of Chrome 71). Google has categorized the bug as “high severity,” however it has so far to regulate the flaw bounty it will give to the analysts who revealed it.
The fixes have already been employed to generate a PoC effort that clashes the Electron development framework and Chrome. But, there is no indications that the bug has been employed for harmful intentions. The creator of SQLite, Dr. D. Richard Hipp affirmed suspicion of someone on Hacker News that the bug only influences systems that judge and attempt absolute SQLite queries, rather than entire applications that merely employ SQLite for database management.
“The vulnerability only exists in applications that allow a potential attacker to run arbitrary SQL. If an application allows that, it is usually called an ‘SQL Injection’ vulnerability and is the fault of the application, not the database engine. The one notable exception to this rule is WebSQL in Chrome,” Hipp explained.