#AZURE POSTGRESQL UPDATE#
#AZURE POSTGRESQL CODE#
#AZURE POSTGRESQL SERIES#

You can optionally disable enforcing TLS connectivity.

The TLS parameter varies based on the connector, for example 'ssl=true' or 'sslmode=require' or 'sslmode=required' and other variations. Likewise, connection strings that are pre-defined in the 'Connection Strings' settings under your server in the Azure portal include the required parameters for common languages to connect to your database server using TLS. To learn more, see planned certificate updates Enforcing TLS connectionsДЇor all Azure Database for PostgreSQL servers provisioned through the Azure portal and CLI, enforcement of TLS connections is enabled by default.

#AZURE POSTGRESQL UPDATE#

Please update your application to use the new certificate. Last year, they disclosed the details of a Cosmos DB vulnerability they named ChaosDB and an App Service flaw named NotLegit.SSL root certificate is set to expire starting Febru().

This is not the first time Wiz researchers have identified potentially serious vulnerabilities in Microsoft cloud services. Wiz concluded that вЂњcustomers of Azure Database for PostgreSQL Flexible Server in any region configured with public network access, regardless of firewall rules, were vulnerable.вЂќ Single Server instances or Flexible servers with the explicit VNet network configuration (private access) were not affected. They could then scan the subnet for the targeted instance and exploit the authentication bypass vulnerability to gain read access to the targetвЂ™s database, which can store sensitive data.

#AZURE POSTGRESQL CODE#

Once that was done, the attacker could have exploited the first vulnerability on their own instance to escalate privileges and achieve arbitrary code execution. In the next phase of the attack, the attacker would identify the targetвЂ™s Azure region - this can be done by matching the database domainвЂ™s IP to AzureвЂ™s public IP ranges - and then create a database in that region. The attacker then needed to acquire a specially crafted certificate with a forged common name matching the one of the target. In an ExtraReplica attack, the attacker first needed to identify the targeted PostgreSQL Flexible Server instance and retrieve its common name and unique identifier from certificate transparency services. Since the security holes affect cloud services, no CVE identifiers have been assigned, but Wiz believes a cloud vulnerability database would be very useful to organizations. The researchers identified two vulnerabilities: a privilege escalation flaw and a cross-account authentication bypass leveraging a forged certificate. Wiz said Microsoft awarded its researchers a $40,000 bug bounty - the amount can be viewed as confirmation of the vulnerabilityвЂ™s severity. ItвЂ™s unclear how many databases were exposed by the vulnerabilities. Azure customers do not need to take any action and the tech giant said it had no evidence of malicious exploitation attempts. Microsoft was informed about the vulnerabilities in January and implemented patches within 48 hours. вЂњBy exploiting an elevated permissions bug in the Flexible Server authentication process for a replication user, a malicious user could leverage an improperly anchored regular expression to bypass authentication to gain access to other customersвЂ™ databases,вЂќ Microsoft said in its own blog post published on Thursday. They impacted Azure Database for PostgreSQL Flexible Server, a fully managed PostgreSQL database-as-a-service offering. The security holes discovered by Wiz researchers are collectively tracked as ExtraReplica - the name stems from the fact that the flaws affected a database replication feature.

#AZURE POSTGRESQL SERIES#

Cloud security company Wiz has released the details of a series of critical vulnerabilities that could have been exploited to access databases belonging to Azure customers.

Azure postgresql