Skip to content

Commit 24d85a4

Browse files
kneeraj2000vedharish
authored andcommitted
docs: adds report contents and other points
1 parent dc78fff commit 24d85a4

File tree

1 file changed

+19
-2
lines changed

1 file changed

+19
-2
lines changed

SECURITY.md

Lines changed: 19 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,27 @@
11
# Reporting Security Vulnerabilities
22

3-
BrowserStack Community take all security vulnerabilities seriously. Thank you for improving the security of our open source software. We appreciate your efforts and responsible disclosure and will make every effort to acknowledge your contributions.
3+
BrowserStack Community take all security vulnerabilities seriously. Thank you for improving the security of our open source software. We appreciate your efforts and responsible disclosure. We will make every effort to acknowledge your contributions.
44

55
Please do NOT raise a GitHub Issue to report a security vulnerability. If you believe you have found a security vulnerability, report it by emailing the BrowserStack security team at:
66

77
88

9-
We ask that you do not use other channels or contact project contributors directly.
9+
Please include as much of the information listed below as you can to help us better understand and resolve the issue:
10+
11+
* The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting)
12+
* Full paths of source file(s) related to the manifestation of the issue
13+
* Any special configuration required to reproduce the issue
14+
* Step-by-step instructions to reproduce the issue
15+
* Proof-of-concept or exploit code (if possible)
16+
* Impact of the issue, including how an attacker might exploit the issue
17+
18+
This information will help us triage your report more quickly.
19+
20+
# Please don't do the following
21+
22+
- Do not take advantage of the vulnerability or problem you have discovered.
23+
- Do not reveal the problem to others until it has been resolved.
24+
- Do not use other channels or contact project contributors directly.
1025

1126
# Disclosure Policy
1227

@@ -15,3 +30,5 @@ When the security team receives a security bug report, they will assign it to th
1530
* Confirm the problem and determine the affected versions.
1631
* Audit code to find any potential similar problems.
1732
* These fixes will be released as fast as possible.
33+
34+
**Vulnerabilities found in this software are not eligible for any kind of bounty rewards and BrowserStack will not be responsible for issuing any CVE for the found security issue.**

0 commit comments

Comments
 (0)