Microsoft Azure DevOps Bounty Program

N/A: vulnerabilities resulting in the listed security impact do not qualify for this severity category

A high-quality report provides the information necessary for an engineer to quickly reproduce, understand, and fix the issue. This typically includes a concise write up or video containing any required background information, a description of the bug, and a proof of concept (PoC). Sample high- and low-quality reports are available here. 

We recognize some issues are extremely difficult to reproduce and understand and will take this into consideration when assessing the quality of a submission.

IN-SCOPE VULNERABILITIES

The following are examples of vulnerabilities that may lead to one or more of the above security impacts:

• Cross site scripting (XSS)
• Cross site request forgery (CSRF)
• Cross-tenant data tampering or access
• Insecure direct object references
• Insecure deserialization
• Injection vulnerabilities
• Server-side code execution
• Significant security misconfiguration (when not caused by user)
• Using component with known vulnerabilities
  • Requires full proof of concept (PoC) of exploitability. For example, simply identifying an out of date library would not qualify for an award
• Unauthorized cross-tenant data tampering or access

WHAT ARE THE RULES GOVERNING THE TESTING OF BOUNTY-ELIGIBLE MICROSOFT ONLINE SERVICES?

The fMicrosoft Azure DevOps Bounty program's scope is limited to technical vulnerabilities in Azure DevOps related products and services. The following are not permitted:

• Any kind of Denial of Service testing.
• Performing automated testing of services that generates significant amounts of traffic.
• Gaining access to any data that is not wholly your own. For example, you are allowed and encouraged to create a small number of test accounts and/or trial tenants for the purpose of demonstrating and proving cross-account or cross-tenant data access. However, it is prohibited to use one of these accounts to access the data of a legitimate customer or account.
• Moving beyond “proof of concept” repro steps for server-side execution issues (e.g proving that you have sysadmin access with SQLi is acceptable, running xp_cmdshell is not).
• Attempting phishing or other social engineering attacks against others, including our employees. The scope of this program is limited to technical vulnerabilities in specified products and services.
• Using our services in a way that violates the terms for that service.

Even with these prohibitions, Microsoft reserves the right to respond to any actions on its networks that appear to be malicious.

OUT OF SCOPE VULNERABILITIES

Microsoft is happy to receive and review every submission on a case-by-case basis, but some submission and vulnerability types may not qualify for bounty reward. Here are some of the common low-severity or out of scope issues that typically do not earn bounty rewards:

• Publicly-disclosed vulnerabilities which have already been reported to Microsoft, or are already known by the wider security community (refer to the Azure DevOps Developer Community as an additional resource)
• Vulnerabilities in any version other than Public Preview and RC releases of Azure DevOps and Azure DevOps Server
• Vulnerabilities that are addressed via product documentation updates, without change to product code or function. 
• Vulnerabilities based on user configuration or action, for example:
  • Vulnerabilities based on user-generated content
  • Vulnerabilities requiring extensive or unlikely user actions
  • Security misconfiguration of a service by a user, such as the enabling of HTTP access on a storage account to allow for man-in-the-middle (MiTM) attacks.
  • Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”)
• Vulnerabilities based on third parties, for example:
  • Vulnerabilities in third-party software provided by Azure such as gallery images and ISV applications
  • Vulnerabilities in third-party extensions
  • Vulnerabilities in platform technologies that are not unique to Azure DevOps and Azure DevOps Server (for example IIS, OpenSSL etc.)
• Out of scope vulnerability types, including:
  • Server-side information disclosure
  • Sub-Domain Takeovers
  • Denial of service (DoS) attacks
  • Cookie replay vulnerabilities
  • Vulnerabilities used to enumerate or confirm the existence of users or tenants
• Vulnerabilities in other Microsoft Products, for example:
  • Vulnerabilities in Hyper-V such as virtual machine escapes. These submissions may be eligible for a bounty through the Mitigation Bypass Bounty program or the Hyper-V Bounty program.
  • Please see the full list of Bounty Programs for other bounty eligible Microsoft products and services.  
• Vulnerability patterns or categories for which Microsoft is actively investigating broad mitigations. As of June 2023, for example, these include, without limitation:
  • Dependency Confusion issues

Microsoft may reject any submission that it determines (in its sole discretion) falls into any of these categories even if otherwise eligible for bounty.

BOUNTY AWARDS

• Microsoft retains sole discretion in determining award amounts and which submissions eligible and in scope.
• There are no restrictions on the number of qualified submissions an individual submitter may provide or number of awards a submitter may receive.
• If we receive multiple bug reports for the same issue from different parties, the bounty will be granted to the first submission. 
• If a duplicate report provides us new information that was previously unknown to Microsoft, we may award a differential to the duplicate submission.  
• If a submission is potentially eligible for multiple bounty programs, you will receive single highest payout award from a single bounty program 

ADDITIONAL INFORMATION

For additional information please see our FAQ.

REVISION HISTORY