Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Contribution] Azure OpenAI Control Plane Bypass for Deployment resource #281

Open
tyson-trust opened this issue Mar 5, 2024 · 2 comments
Labels
addition New security issue or vulnerability azure Issue related to an Azure service

Comments

@tyson-trust
Copy link

tyson-trust commented Mar 5, 2024

title: Azure OpenAI Control Plane Bypass for Deployment resource
slug: azure-openai-controlplanebypass-deployments
cves: null
affectedPlatforms:

  • Azure
    affectedServices:
  • OpenAI
  • Deployment resource
    image: https://raw.githubusercontent.com/wiz-sec/open-cvdb/main/images/[slug].jpg
    severity: Medium - CVSS, Low - Piercing
    piercingIndexVector: A3:1.05/A4:1/A5:1/A6:3/A7:1.1/A8:1.1
    discoveredBy:
    name: Tyson Garrett
    org: TrustOnCloud
    domain: null
    twitter: null
    publishedAt: 2024/02/22
    disclosedAt: 2023/10/24
    exploitabilityPeriod: Ongoing
    knownITWExploitation: null
    summary: |
    A set of Azure OpenAI authoring API’s enables the use of the service instance endpoint as opposed to management.azure.com to create, update, delete, and list/read the Azure OpenAI Deployment resource. This allows for bypass of Azure Policy for Deny/Modify effects, Resource Locks and provides you the option to use access keys instead of your Entra ID identity to do so.

manualRemediation: |
Do not use the Azure AI Developer built-in role and ensure any roles used for Microsoft.CognitiveServices namespace add the below operations to the NotDataActions section of any applicable Role Definitions.

Microsoft.CognitiveServices/accounts/OpenAI/deployments/read
Microsoft.CognitiveServices/accounts/OpenAI/deployments/write
Microsoft.CognitiveServices/accounts/OpenAI/deployments/delete

detectionMethods: null
contributor: https://github.com/tyson-trust
references:

@tyson-trust tyson-trust added the addition New security issue or vulnerability label Mar 5, 2024
@labyrinthinesecurity
Copy link
Contributor

Thanks for the submission!
Maybe we should add that there is no long term fix at the moment, because MSFT doesn't consider this design error as a security vulnerability.

@korniko98
Copy link
Collaborator

@tyson-trust could you add a PR with this information? also - i'm having trouble understanding the impact of this issue and how likely it is to exploit - i think it would be useful to add a POC to the original blogpost.

@korniko98 korniko98 added the azure Issue related to an Azure service label Apr 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
addition New security issue or vulnerability azure Issue related to an Azure service
Projects
None yet
Development

No branches or pull requests

3 participants