Skip to main content

#ChaosDB / Vulnerability in the Azure Cosmos DB Jupyter Notebook

By

On August 21, 2021, an Azure CosmosDB vulnerability was reported for all Azure CosmosDB instances that are using Jupyter Notebooks. Using an active Jupyter Notebook an attacker was able to put his hands on the Azure CosmosDB keys that could be used to get access to the Azure CosmosDB.

Wizz.io describes in detail how somebody can use the vulnerability to steal the primary keys of the Azure CosmosDB instance. The vulnerability is serious because provides full access to Azure CosmosDB instance, including the data itself. 
Microsoft Security Response Center provided a response to this vulnerability, including what were the actions that were taken by the Azure team to mitigate the problem.

You can find below key facts that we need to be aware when you talk about #ChaosDB

  • If you did not receive a notification over email or from Azure Portal you were not affected 
  • Until now Microsoft was not able to identify CosmosDB customers data that were accessed using this vulnerability by 3rd parties or security researches
  • Using Azure Diagnostic Logs you can identify all IPs that access the Azure CosmosDB, including the unusual ones. 
  • There is no way for a customer to know if their Jupyter Notebook integration with Azure CosmosDB was enabled. You can open a ticket to the Microsoft team to find out if the feature was enabled for your account. 
  • Microsoft notified over email and Azure Portal all customers that were affected by the vulnerability
  • The feature was disabled for all customers once the vulnerability was confirmed. 
  • If you activate the functionality, but you don't use it, it will be disabled automatically, as for other festures of Azure
  • The vulnerability existing only for Azure CosmosDB customers that were using Jupyter Notebook or created an Azure CosmosDB instance between 7-13 August 2021
  • A part of Azure Cosmos DB Jupyter notebooks features is in public preview. In general, customers are not using cloud services that are in public preview for production systems. 
What your team should do in the future:
  1. Establish a key/token rotation policy for all cloud and non-cloud resources where access is based on a key or token.
  2. Activate and use Azure Diagnostic Logs and Azure Defender to identify and spot unusual IPs that access your systems. 
    1. Azure Security Center - Alerts for Azure Cosmos DB
    2. Advanced Threat Protection for Azure Cosmos DB
  3. Don't use in production private and public preview services and features of cloud vendors.
  4. Review and invest in security best practices recommended by Azure CAF and AWS CAF (Cloud Adoption Framework), Azure WAF and AWS WAF (Well-Architecture Framework).
  5. Cloud governance is important, don't ignore it and invest in it.

Comments

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too
Post a Comment
Read more