TRON is an open-source platform for launching highly decentralized applications, new financial primitives, and new interoperable blockchains. It is conducted and supported by the active TRON developer community and is governed by TRON DAO. The TRON protocols rely on a unique consensus mechanism to realize the high TPS of the TRON network, which is far beyond Ethereum, bringing developers a good experience of faster transactions.

TRON DAO looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.

Program Rules

• This Vulnerability Response Process and subsequent bounty reward apply to the following:
  1. Code implementation as seen in the tronprotocol/java-tron GitHub repositories. This includes code in all branches, the master branch, and any release branch
• Researchers/Hackers: while you research/hack, we ask that you please refrain from committing the following:
  1. Denial of Service / Active exploitation against the TRON networks
  2. Social Engineering of developers from the TRON developer community and TRON DAO
  3. Any physical or electronic attempts against the TRON developer community and TRON DAO property and/or data centers
• Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
• Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
• When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
• Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
• Social engineering (e.g., phishing, vishing, smishing) is prohibited.
• Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with the explicit permission of the account holder.

Eligibility

Cannot be a current employee of TRON DAO or previously employed within the last 6 months.

Response Targets

TRON DAO will make its best effort to meet the following SLAs for hackers participating in our program:

We’ll try to keep you informed about our progress throughout the process.

Disclosure Policy

• Please do not discuss the reports' contents or any vulnerabilities (even non-vulnerabilities and resolved ones) outside of the program without express consent from the organization.
• Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with the explicit permission of the account holder.
• Follow HackerOne's disclosure guidelines.

Scope

The scope of the TRON DAO bug bounty program radar covers the integrity of the TRON protocols, such as the blockchain consensus mechanism, resource model, TRON Virtual Machine (TVM), APIs, protocol implementation, etc. Classical client security, as well as the security of cryptographic primitives, is also part of the program. Most HTTPS, gRPC, and JSON-RPC methods and CSRF attacks against them are in scope as well. Please send an email to [email protected] for specifics and details of the scope.

Out-of-scope vulnerabilities

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

• 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.
• Previously known vulnerable libraries without a working Proof of Concept.
• Comma-Separated Values (CSV) injection without demonstrating a vulnerability.
• Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
• Rate limiting or brute-force issues on non-authentication endpoints
• Missing best practices in Content Security Policy.
• Missing HttpOnly or Secure flags on cookies
• Missing email best practices (Invalid, incomplete, or missing SPF/DKIM/DMARC records, etc.)
• 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
• Attacks that the reporter has already exploited themselves, leading to damage
• Attacks requiring access to leaked keys/credentials
• Attacks requiring access to privileged addresses (governance, strategist), except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible. Broken link hijacking is out of scope.

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct, and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep TRON DAO and our users safe!