<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Azure-Devops on CuraSec</title><link>https://curasec.metacog.co.kr/tags/azure-devops/</link><description>Recent content in Azure-Devops on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 22 Jul 2026 12:46:13 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/azure-devops/index.xml" rel="self" type="application/rss+xml"/><item><title>Azure DevOps MCP Server Flaw Lets PR Comments Hijack AI Agents</title><link>https://curasec.metacog.co.kr/insights/2026-07-22-microsoft-azure-devops-mcp-flaw-lets-hidden-pr-comments-hija/</link><pubDate>Wed, 22 Jul 2026 12:46:13 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-22-microsoft-azure-devops-mcp-flaw-lets-hidden-pr-comments-hija/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> If you run Microsoft&amp;rsquo;s official Azure DevOps MCP server for AI code review, disable or restrict the PR-description tool until Microsoft ships a patched version with prompt-injection guardrails; an attacker with only PR-comment access can pivot the agent into unintended projects and exfiltrate output.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> No published IOCs, but build detection for anomalous AI agent cross-project access in Azure DevOps audit logs — unusual MCP tool invocations touching repos outside the agent&amp;rsquo;s expected scope are the behavioral signal to hunt for.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> This illustrates a systemic gap in AI coding-agent deployments: prompt injection via developer workflow inputs can bypass access controls; use this as a prompt to add MCP/AI-agent integration scope to your existing AI governance policy review this quarter.&lt;/li>
&lt;/ul></description></item></channel></rss>