Microsoft cloud databases exposed for thousands of customers in unexploited vulnerability, company says

Security company Wiz discovered a vulnerability in Microsoft Azure that allowed it to read, change or delete the databases of thousands of corporate customers

Microsoft says there’s no evidence the flaw was exploited, but it comes after other recent exploits, including on its Exchange email server software

Reading Time:2 minutes

A security surveillance camera is seen near the Microsoft office building in Beijing on July 20. Photo: AP

Published: 10:20am, 27 Aug 2021Updated: 9:29pm, 27 Aug 2021

Microsoft on Thursday warned thousands of its cloud computing customers, including some of the world’s largest companies, that intruders could have the ability to read, change or even delete their main databases, according to a copy of the email and a cybersecurity researcher.

The vulnerability is in Microsoft Azure’s flagship Cosmos DB database. A research team at security company Wiz discovered it was able to access keys that control access to databases held by thousands of companies. Wiz Chief Technology Officer Ami Luttwak is a former chief technology officer at Microsoft’s Cloud Security Group.

Because Microsoft cannot change those keys by itself, it emailed the customers Thursday telling them to create new ones. Microsoft agreed to pay Wiz US$40,000 for finding the flaw and reporting it, according to an email it sent to Wiz.

“We fixed this issue immediately to keep our customers safe and protected. We thank the security researchers for working under coordinated vulnerability disclosure,” Microsoft told Reuters.

Microsoft’s email to customers said there was no evidence the flaw had been exploited. “We have no indication that external entities outside the researcher (Wiz) had access to the primary read-write key,” the email said.

“This is the worst cloud vulnerability you can imagine. It is a long-lasting secret,” Luttwak told Reuters. “This is the central database of Azure, and we were able to get access to any customer database that we wanted.”

Luttwak’s team found the problem, dubbed ChaosDB, on Aug. 9 and notified Microsoft Aug. 12, Luttwak said.