Skip to main content

Microsoft .NET Core and ASP.NET Core Bug Bounty Program Terms

PROGRAM DESCRIPTION

We are pleased to announce an ongoing .NET Core and ASP.NET Core bug bounty program starting on September 1, 2016. For the duration of the program, we invite you to email secure@microsoft.com to submit vulnerabilities found in the latest release candidates, or RTM version of .NET Core and ASP.NET Core running on Windows, Linux and MacOS. You can install the current RTM version and subsequent betas from https://dot.net/.

Qualified submissions are eligible for payments of $500-$15,000 USD, depending on the quality and complexity of the vulnerability as determined by Microsoft. For extremely high-quality submissions we may pay more than $15,000 USD, at our sole discretion.

WHAT CONSTITUTES AN ELIGIBLE SUBMISSION?

To be eligible for payment, your submissions must meet the following criteria:

  • Your report must identify an original and previously unreported vulnerability in the latest RTM version, or supported Beta or RC releases of latest versions of Microsoft .NET Core, ASP.NET Core and the default ASP.NET Core templates provided with the ASP.NET Web Tools Extension for Visual Studio 2015 or later.
  • Vulnerability examples may include bypasses of CSRF protection, Encoding, Data Protection failures, Information disclosures to a client, Authentication bypasses and Remote Code Execution.
  • The vulnerability must both be submitted on and reproduce on the latest RTM version, or on supported Beta or RC releases above the current RTM version.
  • To facilitate quick reproduction of the vulnerability, we request that you include complete and easily understood instructions to reproduce the vulnerability. As shown in the payment table below, high-quality instructions support a higher bounty payment.

Microsoft may reject any submission that it determines does not meet these criteria, at its sole discretion.

HOW ARE PAYMENT AMOUNTS SET?

  • Bounties ranging from $500 - $15,000 USD will be paid out at Microsoft’s discretion based on the quality and complexity of the vulnerability. Microsoft retains sole discretion in determining which submissions are qualified.
  • If we receive multiple bug reports for the same issue from different parties, the bounty will be granted to the first submission based on the criteria mentioned above
  • If a duplicate report provides new information that was previously unknown to Microsoft, we will award a differential to the duplicate submission
  • The first external report received on an internally known issue will receive a maximum of $1,500 USD.
  • If you do not wish to receive a bounty payment for your vulnerability submission, Microsoft will gladly work with you to donate the bounty to an approved charity.

The payment range for eligible submissions will be based upon the following:

Vulnerability typeProof of conceptFunctioning ExploitWhitepaper / Report QualityPayout range (USD)
Remote Code ExecutionRequiredRequiredHighUp to $15,000
RequiredNoHighUp to $6,000
RequiredNoLowUp to $1,500
Security Design FlawRequiredRequiredHighUp to $10,000
RequiredOptionalHighUp to $5,000
RequiredNoLowUp to $1,500
Elevation of PrivilegeRequiredRequiredHighUp to $10,000
RequiredNoLowUp to $5,000
Remote DoSRequiredOptionalHighUp to $5,000
RequiredNoLowUp to $2,500
Tampering / SpoofingRequiredOptionalHighUp to $5,000
RequiredNoLowUp to $2,500
Information LeaksRequiredOptionalHighUp to $2,500
RequiredNoLowUp to $750
Template CSRF or XSSRequiredOptionalHighUp to $2,000
RequiredOptionalLowUp to $500

*Higher payouts are possible, at Microsoft’s sole discretion, based on entry quality and complexity

WHAT CONSTITUTES AN INELIGIBLE SUBMISSION?

The aim of the bug bounty program is to uncover significant vulnerabilities that have a direct and demonstrable impact on the security of our users and our users’ data. While we encourage any submissions that describe security vulnerabilities in ASP.NET, the following are examples of vulnerabilities that will not earn a bounty reward under this program:

  • Publicly-disclosed vulnerabilities which are already known to Microsoft and the wider security community
  • Vulnerabilities in user-generated content
  • Vulnerabilities requiring extensive or unlikely user actions
  • Vulnerabilities which disable or do not use any built in mitigation mechanisms
  • Low impact CSRF bugs
  • Server-side information disclosure
  • Vulnerabilities in platform technologies that are not unique to .NET Core or ASP.NET Core (for example IIS, OpenSSL etc.)

We reserve the right to 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.

.NET and ASP.NET BUG BOUNTY PROGRAM TIMELINES

Program NameStart DateEnding DateAnnouncement Link
CoreCLR and ASP. NET 5 Technical Preview BountyOctober 20, 2015January 20, 2016 https://blogs.msdn.microsoft.com/webdev/2015/10/20/net-core-and-asp-net-launches-a-beta-bug-bounty-program/
NET Core and ASP.NET Core RC2 Bug BountyJune 7, 2016September 7, 2016 https://blogs.msdn.microsoft.com/webdev/2016/06/07/announcing-a-new-net-and-asp-net-core-bug-bounty/
Microsoft .NET Core and ASP.NET Core Bug BountySeptember 1, 2016Ongoing https://blogs.msdn.microsoft.com/webdev/2016/09/01/announcing-the-ongoing-bug-bounty-for-net-core-and-asp-net-core/

BOUNTY PROGRAM FREQUENTLY ASKED QUESTIONS AND PROGRAM REQUIREMENTS

It is your responsibility to comply with the Microsoft Bounty Program – Comprehensive Terms listed in the FAQ. Please see the Microsoft Bounty Program FAQ to get detailed instructions on:

  1. Reporting bugs to Microsoft
  2. Microsoft’s triage and payment process
  3. Eligibility criteria for participation
  4. Bounty payment policies
  5. Your confidentiality obligations
  6. Microsoft’s privacy statement and legal notice
  7. Other questions on the various Microsoft bounty programs

Thank you for participating in the Microsoft Bug Bounty Program!

MSRC Blog

SRD Blog

Microsoft .NET Core and ASP.NET Core Bug Bounty Program Terms