PROGRAM DESCRIPTION

The Microsoft Online Services Bounty Program invites researchers across the globe to identify and sumbit vulnerabilities in specific Microsoft domains and endpoints. Qualified submissions are eligible for bounty rewards of $500 to $20,000 USD.

Bounties will be awarded at Microsoft’s discretion based on the severity and impact of the vulnerability and the quality of the submission, and subject to the Microsoft Bounty Terms and Conditions

IN-SCOPE SERVICES AND PRODUCTS

Most vulnerabilities submitted in the following services are eligible under this bounty program:

  • Office 365
  • Microsoft Account

For a detailed list, please see the In-Scope Domains and Endpoints section of on this page.

Related Cloud Bounty Programs

Submissions identifying vulnerabilities in Azure, Azure DevOps, or Microsoft-identity related online services will be considered under the Azure Bounty Program, Azure DevOps Bounty Program, Microsoft Dynamics 365 Bounty Program or the Microsoft Identity Bounty Program. All submissions are reviewed for bounty eligibility, so don’t worry if you aren’t sure where your submission fits. We will route your report to the appropriate program. 

GETTING STARTED

Please create a test account and test tenants for security testing and probing.

  • For Office 365 services, you can set up your test account here.
  • For Microsoft Account, you can set up your test account here.
  • Learn more about Office 365 on our docuentation page here

In all cases, where possible, include the string “MSOBB” in your account name and/or tenant name in order to identify it as being in use for the bug bounty program.

WHAT CONSTITUTES AN ELIGIBLE SUBMISSION ?

The goal of the Microsoft Bug Bounty program is to uncover significant technical vulnerabilities that have a direct and demonstrable impact on the security of our customers. Vulnerability submissions must meet the following criteria to be eligible for bounty awards:

  • Identify a previously unreported vulnerability in one of the in-scope services or products
  • Include clear, concise, and reproducible steps, either in writing or in video format
    • Providing our engineers with the information necessary to quickly reproduce, understand, and fix the issue allows submissions to be processed as quickly as possible and supports higher bounty awards

Microsoft may reject any submission at our sole discretion that we determine does not meet the above criteria.

HOW ARE AWARD AMOUNTS SET? 

Bounty awards range from $500 up to $20,000. Higher payouts are possible, at Microsoft’s sole discretion, based on the severity and impact of the vulnerability and the quality of the submission. Researchers who provide submissions that do not qualify for bounty awards may still be eligible for public acknowledgment if their submission leads to a vulnerability fix, and points in our Researcher Recognition Program

Security Impact

Report Quality

Severity

Critical

Important

Moderate

Low

Remote Code Execution

High

Medium

Low

$20,000

$15,000

$10,000

$15,000

$10,000

$5,000

$0

$0

Elevation of Privilege

High

Medium

Low

$8,000

$4,000

$3,000

$5,000

$2,000

$1,000

$0

$0

Information Disclosure

High

Medium

Low

$8,000

$4,000

$3,000

$5,000

$2,000

$1,000

$0

$0

Spoofing

High

Medium

Low

N/A

$3,000

$1,200

$500

$0

$0

Tampering

High

Medium

Low

N/A

$3,000

$1,200

$500

$0

$0

Denial of Service

High/Low

Out of Scope

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 an attached proof of concept (PoC). Sample high- and low-quality reports are available here.  

We recognize that some issues are extremely difficult to reproduce and understand, and this will be considered 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 

IN-SCOPE DOMAINS AND ENDPOINTS

Only the following domains and endpoints are eligible for bug bounty awards. Subdomains of in-scope domain are also considered in-scope. Testing for vulnerabilities should only be performed on tenants in subscriptions/accounts owned by the program participant.

Please check “WHOIS” records for all resolved IPs prior to testing to verify ownership by Microsoft. Some third parties host sites for Microsoft under subdomains owned by Microsoft, and these third parties are not in scope for this bug bounty program.

  • www.office.com
  • protection.office.com
  • onedrive.live.com
  • onedrive.com
  • portal.azure.com
  • manage.windowsazure.com
  • azure.microsoft.com/en-us/blog
  • portal.office.com
  • outlook.office365.com
  • outlook.office.com
  • outlook.live.com
  • outlook.com
  • sharepoint.com (excluding user-generated content)
  • lync.com
  • officeapps.live.com
  • www.yammer.com
  • sway.com
  • sway.office.com
  • tasks.office.com
  • teams.microsoft.com
  • asm.skype.com
  • msg.skype.com
  • skyapi.live.net
  • skype.com
  • storage.live.com
  • apis.live.net
  • settings.live.net
  • policies.live.net
  • join.microsoft.com

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

The Microsoft Online Services Bounty Program scope is limited to technical vulnerabilities in online products and services. Activities relying on social engineering or impacting the availability of online services to customers are not permitted, including

  • 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 our employees. The scope of this program is limited to technical vulnerabilities in the specified Microsoft Online 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 SUBMISSIONS AND VULNERABILITIES

MSRC 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 to the wider security community
  • Out of Scope vulnerability types, including:
    • Server-side information disclosure such as IPs, server names and most stack traces
    • Low impact CSRF bugs (such as logoff)
    • Denial of Service issues
    • Sub-Domain Takeovers
    • Cookie replay vulnerabilities
    • URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)
    • ”Cross Site Scripting” bugs in SharePoint that require “Designer” or higher privileges in the target’s tenant
  • Vulnerabilities based on user configuration or action, for example:
    • Vulnerabilities requiring extensive or unlikely user actions
    • Vulnerabilities in user-created content or applications.
      • For example in a *.sharepoint.com domain, if a tenant has publicly exposed their own html page with any kind of vulnerability (i.e. DOM-based XSS) this bug is not eligible for bounty, and will not be accepted as a vulnerability
    • 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 used to enumerate or confirm the existence of users or tenants
  • Vulnerabilities based on third parties, for example:
    • Vulnerabilities in third party software provided by Azure such as gallery images and ISV applications
    • Vulnerabilities in platform technologies that are not unique to the online services in question (for example, Apache or IIS vulnerabilities)
  • Vulnerabilities in the web application that only affect unsupported browsers and plugins

We reserve the right to accept or reject any submission that we determine, in our sole discretion, falls into any of these categories of vulnerabilities even if otherwise eligible for a 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 

Am I eligible for bounty if I find a vulnerability while pentesting Microsoft Azure?

It is your responsibility to comply with the Microsoft Cloud Unified Penetration Testing Rules of Engagement. To receive a bounty, an organization or individual must submit a report identifying a bounty eligible vulnerability to Microsoft using the MSRC submission portal and bug submission guidelines.

TERMS AND CONDITIONS

For additional information on Microsoft bounty program requirements and legal guidelines please see our Bounty Terms and our FAQ.

Thank you for participating in the Microsoft Bug Bounty Program!

 

 

REVISION HISTORY

  • September 2014: Program launched.
  • April 2015: Program scope updated.
  • August 2015: Program scope updated and bounty program name changed from Online Services to Cloud bounty program.
  • July 17, 2018: identity related vulnerabilities moved into the Microsoft Identity Bounty Program. (https://www.microsoft.com/msrc/bounty-microsoft-identity)
  • December 7, 2018: Updated program introduction, FAQ link, and added revision history section.
  • January 17, 2019: Updated award ranges based on impact, severity, and report quality. Added in-scope summary.
  • June 12, 2019: Added outlook.live.com to bounty scope.
  • July 17, 2019: Added Skype.com and tasks.office.com to bounty scope
  • August 5, 2019: Cloud Bounty Program seperated into Online Services Bounty Program and Azure Bounty Program. Azure-related scope moved to Azure Bounty Program. Updated pentesting guidance.