|
@@ -4,7 +4,7 @@
|
|
|
|
|
|
Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/Microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/).
|
|
Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/Microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/).
|
|
|
|
|
|
-If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://docs.microsoft.com/en-us/previous-versions/tn-archive/cc751383(v=technet.10)), please report it to us as described below.
|
|
|
|
|
|
+If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](<https://docs.microsoft.com/en-us/previous-versions/tn-archive/cc751383(v=technet.10)>), please report it to us as described below.
|
|
|
|
|
|
## Reporting Security Issues
|
|
## Reporting Security Issues
|
|
|
|
|
|
@@ -12,19 +12,19 @@ If you believe you have found a security vulnerability in any Microsoft-owned re
|
|
|
|
|
|
Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://msrc.microsoft.com/create-report).
|
|
Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://msrc.microsoft.com/create-report).
|
|
|
|
|
|
-If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://www.microsoft.com/en-us/msrc/pgp-key-msrc).
|
|
|
|
|
|
+If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://www.microsoft.com/en-us/msrc/pgp-key-msrc).
|
|
|
|
|
|
You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://www.microsoft.com/msrc).
|
|
You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://www.microsoft.com/msrc).
|
|
|
|
|
|
Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
|
|
Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
|
|
|
|
|
|
- * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
|
|
|
|
- * Full paths of source file(s) related to the manifestation of the issue
|
|
|
|
- * The location of the affected source code (tag/branch/commit or direct URL)
|
|
|
|
- * Any special configuration required to reproduce the issue
|
|
|
|
- * Step-by-step instructions to reproduce the issue
|
|
|
|
- * Proof-of-concept or exploit code (if possible)
|
|
|
|
- * Impact of the issue, including how an attacker might exploit the issue
|
|
|
|
|
|
+- Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
|
|
|
|
+- Full paths of source file(s) related to the manifestation of the issue
|
|
|
|
+- The location of the affected source code (tag/branch/commit or direct URL)
|
|
|
|
+- Any special configuration required to reproduce the issue
|
|
|
|
+- Step-by-step instructions to reproduce the issue
|
|
|
|
+- Proof-of-concept or exploit code (if possible)
|
|
|
|
+- Impact of the issue, including how an attacker might exploit the issue
|
|
|
|
|
|
This information will help us triage your report more quickly.
|
|
This information will help us triage your report more quickly.
|
|
|
|
|