Microsoft Patches Critical Copilot Studio Vulnerability Exposing Sensitive Data

Microsoft Patches Critical Copilot Studio Vulnerability Exposing Sensitive Data

August 21, 2024 at 12:36PM

Researchers have uncovered a critical security flaw in Microsoft’s Copilot Studio (CVE-2024-38206) that allows unauthorized access to sensitive information. Microsoft has addressed the vulnerability and stated no customer action is required. The disclosure follows the announcement of security flaws in Microsoft’s Azure Health Bot Service and the upcoming enforcement of multi-factor authentication for Azure customers.

Key takeaways from the meeting notes are as follows:

– A critical security flaw impacting Microsoft’s Copilot Studio (CVE-2024-38206) has been disclosed, allowing an authenticated attacker to bypass Server-Side Request Forgery (SSRF) protection and leak sensitive information over a network.

– The vulnerability has been addressed by Microsoft, and no customer action is required.

– Tenable security researcher Evan Grant discovered and reported the vulnerability, which exploited Copilot’s ability to make external web requests, allowing access to Microsoft’s internal infrastructure for Copilot Studio.

– The attack technique made it possible to retrieve instance metadata in a Copilot chat message, use it to obtain managed identity access tokens, and gain read/write access to a Cosmos DB instance.

– While the approach does not allow access to cross-tenant information, the shared infrastructure powering the Copilot Studio service could potentially affect multiple customers when having elevated access to Microsoft’s internal infrastructure.

– Microsoft disclosed two now-patched security flaws in Azure Health Bot Service (CVE-2024-38109, CVSS score: 9.1), which could permit a malicious actor to achieve lateral movement within customer environments and access sensitive patient data.

– Microsoft will require all Azure customers to have enabled multi-factor authentication (MFA) on their accounts starting October 2024 as part of its Secure Future Initiative (SFI).

– Gradual enforcement for MFA at sign-in for Azure CLI, Azure PowerShell, Azure mobile app, and Infrastructure as Code (IaC) tools will start in early 2025.

Please let me know if you need any additional information or if there are any specific actions to be taken based on these meeting notes.

Full Article