Saturday, April 5, 2025
HomeVulnerabilityCritical Vulnerability in Azure Synapse Let Attackers Control other Customers’ Workspaces

Critical Vulnerability in Azure Synapse Let Attackers Control other Customers’ Workspaces

Published on

SIEM as a Service

Follow Us on Google News

The Microsoft Azure Synapse service has been identified as unsafe to use, and Orca Security has issued a security advisory for CVE-2022-29972. 

It was found that the integration runtime (IR) used by the Azure-affected services to connect to Amazon Redshift is vulnerable to this security hole in the third-party Open Database Connectivity (ODBC) data connector.

IR users, including multiple tenants, could have been affected by the flaw if a remote attacker exploited it. Here’s what Microsoft stated:-

“These certificates are specific to Azure Data Factory and Synapse Pipelines and do not pertain to the rest of Azure Synapse. The vulnerability could have allowed an attacker to perform remote command execution across IR infrastructure not limited to a single tenant.”

There was no evidence of exploitation of the vulnerability prior to the release of the patch, even though the vulnerability was mitigated on April 15.

Disclosure Timeline

Here below we have mentioned the timeline:-

  • January 4: Orca reported the issue to Microsoft.
  • March 2: Microsoft completed the rollout of the initial hotfix.
  • March 11: Microsoft identified and notified the customer affected by the researcher’s activity.
  • March 30: Orca notified Microsoft of an additional attack path to the same vulnerability.
  • April 13: Orca notified Microsoft of a second attack path to the same vulnerability.
  • April 15: Additional fixes deployed for the two newly reported attack paths as well as additional defense-in-depth measures applied.

Mitigation

To mitigate this problem, Azure cloud customers and on-premises customers with auto-updates enabled do not have to take any further steps. 

Azure Service Health Alerts are already letting Self-Hosted IR customers who don’t have auto-updates enabled on their deployments know that they should secure their deployments in order to prevent further issues.

On Microsoft’s Download Center, the company recommends the update of their self-hosted integrated reports (5.17.8154.2) to the most current version.

The “Customer Recommendations and Additional Support” section contains further information on how to mitigate CVE-2022-299.

Apart from this, 64-bit systems with the latest version of .NET Framework can install these updates, including the latest versions.

Azure’s security vulnerabilities have already been fixed twice in the past year, including by Microsoft in March. In December, a vulnerability was found, called AutoWarp, that allowed attackers to take complete control of another.

Wiz researchers also found Azure Cosmos DB, a software agent for Open Management Infrastructure (OMI), and Azure App Service to be vulnerable to the same vulnerabilities that Redmond patched up in the past year.

You can follow us on LinkedinTwitterFacebook for daily Cybersecurity and hacking news updates.

Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

Ivanti Fully Patched Connect Secure RCE Vulnerability That Actively Exploited in the Wild

Ivanti has issued an urgent security advisory for CVE-2025-22457, a critical vulnerability impacting Ivanti...

Beware! Weaponized Job Recruitment Emails Spreading BeaverTail and Tropidoor Malware

A concerning malware campaign was disclosed by the AhnLab Security Intelligence Center (ASEC), revealing...

EncryptHub Ransomware Uncovered Through ChatGPT Use and OPSEC Failures

EncryptHub, a rapidly evolving cybercriminal entity, has come under intense scrutiny following revelations of...

PoisonSeed Targets CRM and Bulk Email Providers in New Supply Chain Phishing Attack

A sophisticated phishing campaign, dubbed "PoisonSeed," has been identified targeting customer relationship management (CRM)...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Chinese Hackers Exploit Ivanti VPN Vulnerability to Deliver Malware Payloads

Ivanti disclosed a critical security vulnerability, CVE-2025-22457, affecting its Connect Secure (ICS) VPN appliances,...

Vite Development Server Flaw Allows Attackers Bypass Path Restrictions

A critical security vulnerability, CVE-2025-31125, has been identified in the Vite development server.Due to improper...

Critical Apache Parquet Vulnerability Allows Remote Code Execution

A severe vulnerability has been identified in the Apache Parquet Java library, specifically within...