Emercury Bug Bounty Program Bug Bounty Program

Bug Bounty Scope

The following websites are within the scope of the program:

Non-Intrusive Submissions Handling

The following section encompasses submission of the vulnerabilities that do not require intrusive testing as per Open Bug Bounty rules:

General Requirements:

The requirement for the security check is to find and report high-severity security breaches.
The tests should be done on this domain: https://panel.emercury.net/
You'll need to create a new account here: https://panel.emercury.net/registration.php

Testing Requirements:

* Any vulnerability found must be reported no later than 24 hours after discovery.
* You are not allowed to disclose details about the vulnerability anywhere else.
* You must avoid tests that could cause degradation or interruption of our service.
* You must not leak, manipulate, or destroy any user data.
* You are only allowed to test against accounts you own yourself.
* The use of automated tools or scripted testing is not allowed.

Possible Awards:

The standard reward is $50.

To qualify for a reward under this program, you should:

* Be the first to report a vulnerability.
* Include attachments such as screenshots or proof of concept code as necessary.
* Send a clear textual description of the report along with steps to reproduce the vulnerability.
* Disclose the vulnerability report directly and exclusively to us.

A good bug report should include the following information at a minimum:

* List the URL and any affected parameters
* Describe the browser
* Describe the perceived impact.
How could the bug potentially be exploited?
Any video or screenshot can be helpful.

Special Notes:

Any activity that would disrupt, damage, or adversely affect any third-party data or account is not allowed.

Please do not mass-create accounts to perform testing. Also, do not perform brute force testing to determine whether rate limiting is in place for particular APIs or pieces of functionality.

The following are strictly prohibited:
* Denial of Service attacks.
* Automated tools or scans, botnet, compromised site, end-clients, or any other means of large automated exploitation or use of a tool that generates a significant volume of traffic.

Additionally, the following vulnerabilities will not be considered for bounty:
* Cross-site request forgery (CSRF)
* Cross domain leakage
* Information disclosure
* Software version disclosure
* XSS attacks via POST or headers
* Self-XSS
* Missing SPF or DMARC records
* HttpOnly and Secure cookie flags
* SSL/TLS related (such as HSTS, GET over HTTP, Password sent in HTTP)
* Session timeout
* Session Hijacking (cookie reuse)
* Missing X-Frame or X-Content headers
* Account enumeration
* Click-jacking
* Rate-limiting
* Confirmation Email (anything related with)