Bug Bounty

Responsible Disclosure

Responsible disclosure includes:

  • Providing us a reasonable amount of time to fix the issue before publishing it elsewhere.
  • Making a good faith effort to not leak or destroy any Bitrica user data.
  • Not defrauding Bitrica users or Bitrica itself in the process of discovery.

In order to encourage responsible disclosure, we promise not to bring legal action against researchers who point out a problem provided they do their best to follow the above guidelines.

Eligibility

In general, anything which has the potential for financial loss or data breach is of sufficient severity is eligible, including:

  • XSS
  • CSRF
  • Authentication bypass or privilege escalation
  • Click jacking
  • Remote code execution
  • Obtaining user information
  • Accounting errors

In general, the following would not meet the threshold for severity:

  • Lack of password length restrictions
  • Session-related issues (session fixation etc.)
  • Merely showing that a page can be iFramed without finding a link on the page to be click-jacked.
  • Self-XSS
  • Denial of service
  • Spamming
  • Vulnerabilities in third party applications which make use of the Bitrica API
  • Vulnerabilities which involve privileged access (e.g. rooting a phone) to a victim's device(s)
  • Logout CSRF
  • User existence/enumeration vulnerabilities
  • Password complexity requirements
  • Reports from automated tools or scans (without accompanying demonstration of exploitability)
  • Social engineering attacks against Bitrica employees or contractors
  • Text-only injection in error pages
  • Automatic hyperlink construction by 3rd party email providers
  • Using email mutations (+, ., etc) to create multiple accounts for a single email

Bitrica will determine at its discretion whether a vulnerability is eligible for a reward and the amount of the award.

Please note, while we are still a growing startup we are unable to provide enormous compensation.

Reporting

Please send a detailed step-by-step instruction on how to reproduce the bug to [email protected].

By submitting a bug, you agree to be bound by the above rules.

Thank you for helping keep the community safe!