Azure SDK for Python

Skip to content What this pays sorona.xyz pays 1.25× the program's reward, up to +$1,000 per finding, plus a complexity bonus of up to $1,000 for especially complex or well-chained bugs. Finding │ Program pays │ Through sorona.xyz Critical - deserialization of untrusted data or code injection, high-quality report │ $15,000 │ $16,000 Critical - authentication issues, improper access control, SSRF, or SQL and command injection │ $12,000 │ $13,000 Important - deserialization of untrusted data or code injection │ $10,000 │ $11,000 Critical - XSS, CSRF, cross-origin access, improper input validation, web misconfiguration │ $8,000 │ $9,000 Important - authentication issues, improper access control, SSRF, or SQL and command injection │ $6,000 │ $7,000 Critical - GitHub Actions in the repository │ $5,000 │ $6,000 Important - XSS, CSRF, cross-origin access, improper input validation, web misconfiguration │ $4,000 │ $5,000 Important - GitHub Actions in the repository │ $3,000 │ $3,750 Moderate and Low, every vulnerability type │ $0 │ $0 Submit a vulnerability CVE history 2 Last 12 months 5 Lifetime Auth bypass 35 % Info disclosure 30 % Access control 20 % Parsing/validation 10 % Latest advisories Loading the feed Overview This monorepo is how Python code authenticates to and talks to Azure: azure-core alone records around 235 million PyPI downloads a month, and it sits directly on the credential path for data-science pipelines, Airflow and Databricks jobs, Azure Functions, Kubernetes workloads using workload identity, and effectively every Python application deployed on Azure. Credential-chain and token-handling defects here are cross-tenant by nature rather than by accident, which is exactly why the two most serious historical CVEs in the family, CVE-2024-35255 and CVE-2023-36414, were both identity bugs. Microsoft pays it through the MSRC Researcher Portal on the Open Source Bounty Program, where authentication issues top out at $12,000 for a high-quality Critical report and the $15,000 band needs deserialization or code injection. sorona.xyz adds 1.25x on top of whatever Microsoft awards, up to $1,000 more, plus a complexity bonus of up to $1,000 for a well-chained finding. In scope The whole of azure/azure-sdk-for-python , which the program names on its SCOPE list under "Azure SDKs, limited to the following", at Critical or Important severity on the most recent actively maintained branch azure-core : the sync and async HTTP pipelines, every policy on them, the transport adapters and the tracing hooks each generated client inherits azure-identity : every credential type, the chained credentials, managed and workload identity, the CLI and environment fallbacks, and the token cache The generated service clients across the whole catalogue, azure-storage-* , Key Vault, Cosmos, Service Bus, Event Hubs, App Configuration and the rest: request construction, URL and SAS handling, and response deserialization The azure-mgmt-* control-plane clients, and the shared serialization and azure-common code the generator emits against The repository's own build, release and publish GitHub Actions workflows, which the program prices in a band of their own Out of scope Microsoft and Azure repositories outside the program's fifteen-entry SCOPE list: the standard SECURITY.md pointing at MSRC is a reporting path and funds nothing Azure service-side defects, which belong to the Microsoft Azure bounty program Upstream PyPI dependencies the SDK consumes rather than owns Findings whose impact stays on the local machine, since this repository sits outside the carve-out Microsoft grants to VS Code, Agent Framework, TypeScript, Monaco Editor and PowerShell Moderate and Low severity, which pay $0 at every report quality Samples, tutorials, quickstart code and samples/ directories Hackathon repositories and dependency-confusion reports Publicly disclosed issues Reports Microsoft cannot pay out on: residency in a sanctioned country, or no IRS tax form returned within 30 days of validation, voids the award Most-valued findings Deserialization of an untrusted or spoofed service response in generated client code reaching execution in the calling process: deserialization of untrusted data is the class carrying the $15,000 top band here A credential-chain flaw in azure-identity that makes a process authenticate as an identity it was never meant to assume, the CVE-2024-35255 shape and the $12,000 authentication-issues band Bearer-token or header propagation in the azure-core pipeline that forwards a token across a redirect to a host outside the intended Azure endpoint Token cache handling that lets one tenant's or one principal's cached token be selected for another's request SAS or URL construction in the Storage or Key Vault clients that grants broader access, or reaches a different resource, than the caller asked for SSRF driven by pipeline redirect handling, where a service response steers an authenticated client at an internal endpoint Program rules Submit through sorona.xyz first. We validate, coordinate with the program's security team, and add the payout uplift on top of whatever it awards. Only the eight repositories listed under "Azure SDKs, limited to the following" qualify; no other Azure repository is covered, however similar it looks Azure service-side defects belong to the separate Microsoft Azure bounty program, not this one, so the bug has to live in the client library This repo is not in the local-machine carve-out, so local-machine-only impact is excluded Only Critical and Important severity qualify on the most recent actively maintained branch; Moderate and Low findings pay $0 Follow coordinated vulnerability disclosure: Microsoft requires bounty submissions stay confidential while it fixes, and imposing a fix deadline forfeits eligibility Return an IRS tax form (W-9, W-8BEN or 8233) within 30 calendar days of validation, and expect sanctions screening Disclosure Coordinated through MSRC. Azure SDK fixes are published through the Microsoft Security Update Guide rather than as repository advisories, so the public record and the credit appear there once fixed packages are on PyPI. Microsoft requires bounty submissions stay confidential while it fixes, so file with MSRC yourself first, hold publication until that record appears, and send sorona.xyz the case ID. Safe harbor Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf. You are responsible for understanding and following the laws that apply to you, wherever you are, and for staying within any scope the project has defined. Submit a vulnerability