Azure's Weakest Link – Five Full Cross-Tenant Compromises

320 points · 59 comments on HN · read original →

Points and comments are a snapshot, not live.

Five critical cross-tenant Azure API Connection vulnerabilities earned $200,000.

A security researcher details five critical elevation-of-privilege vulnerabilities in Azure Logic Apps API Connections, netting a $200,000 bug bounty. By exploiting path traversal in ARM REST API endpoints (`DynamicInvoke`, `DynamicList`, etc.) and manipulating the `host.api.RuntimeUrl` parameter, an attacker can compromise any API Connection worldwide, including cross-tenant access to Key Vaults, Azure SQL databases, and external services like Jira or Salesforce. Microsoft fixed each issue, but the fixes were repeatedly bypassed via path traversal and validation timing flaws. The underlying architectural issue-APIM instances having rights to all connections-remains unaddressed.

What commenters are saying

Commenters sharply criticize Microsoft's security track record, noting repeated cross-tenant leaks and sloppy fixes. Many question why enterprises still choose Azure, citing vendor lock-in, bundled licensing, and FedRAMP compliance as key drivers. A recurring thread highlights Microsoft's poor support and internal culture, with one FTE confirming the 'frozen middle' problem. Several comments blame elementary authentication mistakes and outsourcing for the persistent vulnerabilities. One commenter raises a separate but related consent flow issue, while others call the engineering needed to find these bugs a humanitarian concern.