{"id":42545,"date":"2021-08-27T01:16:33","date_gmt":"2021-08-27T01:16:33","guid":{"rendered":"https:\/\/www.threatshub.org\/blog\/azures-now-fixed-cosmos-db-flaw-could-have-been-exploited-to-read-write-any-database\/"},"modified":"2021-08-27T01:16:33","modified_gmt":"2021-08-27T01:16:33","slug":"azures-now-fixed-cosmos-db-flaw-could-have-been-exploited-to-read-write-any-database","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/azures-now-fixed-cosmos-db-flaw-could-have-been-exploited-to-read-write-any-database\/","title":{"rendered":"Azure’s now-fixed Cosmos DB flaw could have been exploited to read, write any database"},"content":{"rendered":"

Infosec outfit Wiz has revealed that Microsoft\u2019s flagship Azure database Cosmos DB could have been exploited to grant any Azure user full admin access \u2013 including the ability to read, write, and delete data \u2013 to any Cosmos DB instance on Azure. Without authorization. For months.<\/p>\n

Wiz has named<\/a> the flaw ChaosDB.<\/p>\n

\u201cBy exploiting a chain of vulnerabilities in the Jupyter Notebook feature of Cosmos DB, a malicious actor can query information about the target Cosmos DB Jupyter Notebook,\u201d reads Wiz\u2019s explanation. \u201cBy doing so, the attacker will obtain a set of credentials related to the target Cosmos DB account, the Jupyter Notebook compute, and the Jupyter Notebook Storage account, including the Primary Key.\u201d<\/p>\n