Skip to content

Latest commit

 

History

History
86 lines (58 loc) · 5.83 KB

SECURITY.md

File metadata and controls

86 lines (58 loc) · 5.83 KB
Raw

🙏 Please report bug directly to [email protected] or just shoot it straight to our official page on BugRap, where our pros got it covered.

Scope

This bug bounty program extends to all code within the OneKey Github Repo.

Bounties for potential bugs include, but are not limited to:

  • Private keys, storage, forensics
  • Task, and CI/CD workflow vulnerabilities
  • Domain hijacking, Secrets compromise
  • Authorization and privilege issues

More generally, if it lives in the repository* and affects OneKey's security, it's fair game.

* There are some components of the OneKey repository that are not created by the OneKey team, but which still could be relevant to overall security. If a bug or exploit makes use of any external libraries or submodules, it will be considered on a case-by-case basis for elegibility.

Rules

Submission Guidelines

All bugs reported must be done through the creation of an issue in the OneKey github repo, or if the submitter wishes to disclose privately, or to remain anonymous by an email sent to [email protected] . Private submissions are still eligible for a bounty.

Unless there is a specific reason for a private disclosure, bugs should be submitted as issues on the OneKey GitHub repository, and tagged with the 'bug' label.

It is requested that all submissions follow the format defined in the issue template -- clarity of description and thoroughness of documentation will be a consideration for reward amount, in addition to impact and likelihood.

In the case of private bug disclosure, all relevant materials should be sent in email to [email protected] -- and should follow the same template as a public issue.

Once submitted, the issue will be responded to, verified, accepted, and rewarded accordindly.

Submission Branches

Participants in the program are free to submit bugs on branches in the OneKey codebase:

  • against the master branch which will be tagged as the mainnet release for deployment

Bug Severity and Bounties

In the same manner as the Ethereum Bug Bounty Program, submissions will be evaluated by the OneKey team according to the OWASP risk rating methodology, which grades based on both Impact and Likelihood.

It is at the sole discretion of OneKey to decide whether or not a bug report qualifies for a bounty, and to determine the severity of the issue

  • P0: $5,000 USD
  • P1: $2,500 USD
  • P2: $1,000 USD
  • P3: $500 USD
  • P4: $250 USD

Severity levels based on

  • The severity of the bug.
  • The likelihood that the bug will affect users.
  • The responsibility of the researcher — did the researcher take destructive action or otherwise harm the functioning of our systems.
  • The role of the researcher — was the researcher the first person to discover the bug, or is the bug based on some public information.
  • How well the report was written and how easy it is to understand.

Issues reported may or may not constitute a security risk for the OneKey contracts. A higher severity will be awarded to vulnerabilities submitted that could potentially result in either the loss of funds, or a situation in which the contracts arrive in an undesirable state that cannot be rectified through existing contract mechanisms, such as 'emergency mode' or through a network upgrade. However, all submitted bugs and vulnerabilities will be considered for prizes.

Ineligible Bugs

Any vulnerabilities or flaws in other software tools created by OneKey (e.g. OneKeyJS, purser, tailor, etc.) are not eligible. Flaws in these software tools are welcome disclosures, but will not be awarded bounties for this bug bounty program.

When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

  • Attacks and vulnerabilities that depend on compromised keys or other security flaws outside the OneKey codebase (keyloggers, intercepted communications, social engineering exploits, etc.).
  • Attacks that are accounted for in the system design, i.e. Ethereum network spamming, malicious reputation mining, malfeasance in OneKey administration.
  • Critiques of the OneKey and overall mechanism design. We welcome suggestions and constructive criticism, and ask that it be directed to [email protected] .
  • Clickjacking on pages with no sensitive actions
  • Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
  • Attacks requiring MITM or physical access to a user's device.
  • Attacks requiring a compromised victim device.
  • Previously known vulnerable libraries without a working Proof of Concept.
  • Comma Separated Values (CSV) injection without demonstrating a vulnerability.
  • Any activity that could lead to the disruption of our service (DoS).
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
  • Rate limiting or bruteforce issues on non-authentication endpoints
  • Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
  • Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
  • Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.
  • Tabnabbing
  • Open redirect - unless an additional security impact can be demonstrated
  • Issues that require unlikely user interaction
  • Perceived security weaknesses without evidence of the ability to demonstrate impact (e.g. Missing best practices, functional bugs without security implications, etc.)