What the demonstration did
Research demonstration / Wiz
- 1
Notebook isolation
August 2021Wiz finds that one Cosmos DB notebook can expose keys belonging to other accounts.
- 2
Database authorization
August 2021The exposed account keys carry broad permissions on the corresponding databases.
Impact
The research established that the keys authorized database reads, writes and deletes. The notification percentage describes customers asked to rotate keys, not confirmed data theft.
Would the controls have stopped it?
Remove account keys as a way into the database
For supported Cosmos DB workloads that can use Microsoft Entra ID, disabling key-based authentication makes a copied primary key unusable for data requests. Affected owners still needed to rotate potentially exposed keys after Microsoft disabled the notebook feature.
Incident control assessments
- 1
- Prevented
- 0
- Contained
- 1
- Not covered
How it could have been prevented
The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.
Research demonstration / Wiz
1 · Notebook isolation
1 Not covered2 · Database authorization
1 PreventedKey facts
- Microsoft introduced Jupyter notebooks for Cosmos DB in 2019.
- New Cosmos DB accounts had notebooks enabled by default starting in February 2021.
- Wiz obtained long-lived primary keys from other Cosmos DB accounts during its research.
- Microsoft disabled the vulnerable notebook feature within 48 hours of the report.
- Wiz reported that Microsoft had notified more than 30% of Cosmos DB customers to rotate their keys.
- Microsoft said it received the report on August 12. Its investigation found no customer data accessed by the researchers or third parties. It asked notified customers to regenerate affected primary read-write keys.
Sources
Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.
- 1.ChaosDB: How we hacked thousands of Azure customers’ databasesWiz Research · Aug 26, 2021 · ResearchThe research established that the keys authorized database reads, writes and deletes. The notification percentage describes customers asked to rotate keys, not confirmed data theft.
- 2.Connect with role-based access control and Microsoft Entra IDMicrosoft · undated · Vendor reportCurrent Cosmos DB documentation explains how disabling key-based authentication requires clients to use Entra authorization.
- 3.Update on the vulnerability in the Azure Cosmos DB Jupyter Notebook FeatureMicrosoft Security Response Center · Aug 27, 2021 · AdvisoryMicrosoft said it received the report on August 12. Its investigation found no customer data accessed by the researchers or third parties. It asked notified customers to regenerate affected primary read-write keys.
The estate in the replay follows the researchers' description of their own test environment. Verdicts describe what a control does when it is in place before the run. They are not an assessment of any company's security program.