Skip to content
NewA calmer, faster ZeroHour

Azure API Connection flaws enable cross-tenant compromise

Original title: Azure’s Weakest Link - Five Full Cross-Tenant Compromises

Lobsters · securityby binarysecurity.no via ohrv ()9 min read1
AI summary · x-ai/grok-4.7Summaries by Vani AI

The researcher says five issues paid $200,000 and can reach Key Vault, Azure SQL and services such as Jira.

A Binary Security write-up describes further flaws in Azure Logic Apps API Connections that let an attacker invoke another tenant’s connection and use its backend token. The author shows a path-traversal request through ARM DynamicInvoke that read a Key Vault secret in a different tenant. After Microsoft marked that issue fixed, the author extracted Logic App code and looked for bypasses of path checks. The post says the issues together paid $200,000 and were presented at Blue Hat Asia 2026.

Unconfirmed: The post does not state whether Microsoft has fixed the later bypasses.

Key facts
  • Abuse uses ARM DynamicInvoke or /extensions/proxy/ against shared API Management.
  • One demonstrated response returned a secret named victimsecret.
  • The author says connection tokens are often broader than least privilege.
  • A prior path-traversal report was marked fixed, then examined for bypasses.
Security assessment · AI, from the articlePublic proof of concept

Impact: Cross-tenant use of victims' API connection backend tokens

ProductAffected
Microsoft Azure API Connections—
What to do
  1. 1.Scope API connection tokens and keys to the minimum backend privileges needed.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

Indicators of compromise

auto-extracted · verify before use · export allAll
TypeIndicatorContext
md57914d45aa60342809fb8cc12dc68b10e"value": "dontreadme", "name": "victimsecret", "version": "7914d45aa60342809fb8cc12dc68b10e", "contentType": null, "isEnabled": true, "createdTime": "2
md588d28f5ff7b642cfb91df184938d074c.." }, "three" : { "value" : "sql" }, "four" : { "value" : "88d28f5ff7b642cfb91df184938d074c" }, "five" : { "value" : "v2" }, "six" : { "value" : "datas
md5cbfb0f4313144117a7440368902bb871ttps://logic-apis-norwayeast.azure-apihub.net/apim/keyvault/cbfb0f4313144117a7440368902bb871?' for the referenced connection. Either omit the 'host.api'
md5fd8d0f4f4069495991ccb4974f96a1ed, "path" : "path/%2e%2e/%2e%2e/%2e%2e/%2e%2e/apim/keyvault/fd8d0f4f4069495991ccb4974f96a1ed/secrets/victimsecret/value" }, } HTTP/2 200 OK Cache-Contro

From the original article

9 min read at binarysecurity.no

In my previous blog posts, Azure’s Weakest Link? and Azure’s Weakest Link - Full Cross-Tenant Compromise , I gave an overview of the severely insecure architecture behind API Connections in Azure, a part of Azure Logic Apps, and an instance of a full cross-tenant compromise using these inherent flaws. Now I am back with some more vulnerabilities in this system, each giving the same primitives to the attacker.

Lobsters · security

By binarysecurity.no via ohrv · binarysecurity.no

Read the full article at Lobsters · security

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.