News for hackers. Stuff that matters.
Re:New ‘Meow’ attack has deleted almost 4k unsecured databases by derefr on Sunday July 26, 2020 @12:11PM (#23958075)
I'm ambivalent about this action in most cases, but in some specific cases there can be a clear reason to have an exposed database: namely when the database is a guest-accessible, read-only repository of public data, i.e. the self-hosted equivalent of publishing a Google BigQuery dataset.

As someone who runs such a "public-access data library" myself, I would be slightly annoyed if someone came along and burned it down, just because it has an unpatched vulnerability.

...but if it got deleted because I left default admin creds on it, though, that'd be my own fault.

Re:New ‘Meow’ attack has deleted almost 4k unsecured databases by jmvoodoo on Sunday July 26, 2020 @12:13PM (#23958088)
Databases that are read only would be unaffected by this attack.
Re:New ‘Meow’ attack has deleted almost 4k unsecured databases by derefr on Sunday July 26, 2020 @12:18PM (#23958109)
Read-only in practice, not inherently read-only in the way that e.g. CD-ROM is. Such systems still need to have their otherwise-static dataset updated "online" by an ETL pipeline agent-user. Which often means, in the DBMSes with less fine-grained security models, that such users need to have full DML (and even DDL) capabilities, rather than only insert capability.
Re:New ‘Meow’ attack has deleted almost 4k unsecured databases by dtech on Sunday July 26, 2020 @12:35PM (#23958229)
This attack was only possible on databases with unsecured or weakly secured read-write access.