Crypterium 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:

We require that all researchers follow the following testing and reporting rules:

If you are able to expose PII (personally identifying information) as a result of your testing, please stop testing and submit the vulnerability and do not include PII in your report submission. This is for compliance reasons.
Stop testing and report the issue immediately if you gain access to any non-public application or non-public credentials.
Only interact with accounts you own or with the explicit permission of the account holder.
Perform research only within the scope set out below.
To the extent that you have accessed non-public Crypterium information in the course of your research, you do not maintain copies of any such information or share any such information with any third party.
You do not publicly disclose or share the vulnerability details without the written permission of Crypterium.

Testing Requirements:

Vulnerability reports which do not include careful manual validation - for example, reports based only on results from automated tools and scanners or which describe theoretical attack vectors without proof of exploitability - will be closed as Not Applicable.

The Crypterium Bug Bounty program consider to exclude vulnerability classes below:

Self-XSS
Tabnabbing
Clickjacking
Flash-based XSS
Cookie expiration
Cookie valid after logout
Issues related to rate limiting
Internal IP address disclosure
Reveal internal class information
Unauthenticated/logout/login CSRF
Cookie valid after password change/reset
Missing best practices in SSL/TLS configuration
Weak password policies & Password policies bypass
Attacks requiring MITM or physical access to a user's device
Any activity that could lead to the disruption of our service (DoS)
Previously known vulnerable libraries without a working Proof of Concept
Weak Captcha & Captcha bypass (excluded only for testing environments)
Login or Forgot Password page brute force and account lockout not enforced
Vulnerabilities only affecting users of outdated or unpatched browsers and platforms
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
Username enumeration on customer-facing systems (i.e. using server responses to determine whether a given account exists)
Vulnerabilities that only affect one browser will be considered on a case-by-case basis and may be closed as informative due to the reduced attack surface
Vulnerability reports that require a large amount of user cooperation to perform, unlikely or unreasonable actions which would be more symptomatic of a social engineering or phishing attack and not an application vulnerability (e.g. disabling browser security features, sending the attacker critical information to complete the attack, guiding the user through a particular flow and requiring them to enter malicious code themselves, etc.)

Possible Awards:

Swag
Monetary rewards (TBD)

Special Notes:

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. Violation of these requirements may result in permanent disqualification from the program.
Any activity determined to involve the intentional compromise of the privacy of our customers or employees or the intentional disruption of the operation of our products, services or IT infrastructure will result in permanent disqualification from the program.

Feedback

If you have suggestions for improving this program, please let us know at [email protected]