8 comments

  • gtowey a minute ago

    > Cosmos DB's engine translated Gremlin queries into .NET code, enforcing a set of restrictions designed to prevent queries from reaching beyond Gremlin operations. These restrictions, however, didn't sufficiently account for .NET reflection

    Wow, this is so unbelievably amateurish.

  • sakisv 2 hours ago

    Is it me or was there a similar vulnerability reported a few years ago? Something about the attacker getting access to all platform's users' databases, though not sure if it was cosmos or something similar.

  • troelsSteegin 2 hours ago

    "Cosmos Master Key"... I can see why that would have been convenient, but talk about a footgun. Right out of a Marvel movie. Still, if admin backdoor access is business-necessary, is the answer a unique admin access key per account?

    • a012 2 hours ago

      This is not the first time M$ “lost” their master key, it’s their tradition now

  • lateral_cloud 2 hours ago

    It took them 6 months to fix this properly?

  • uvuv 4 hours ago

    A critical vulnerability chain in Azure Cosmos DB enabled full read and write access to every Cosmos DB database.

  • redwood 2 hours ago

    Incredible that this is the second time Wiz has discovered a global Cosmos DB vulnerability (https://chaosdb.wiz.io/) and a shock that anyone is trusting Microsoft, Azure or in particular Cosmos DB with anything mission critical