Vulnerability Disclosure Policy
Introduction
The tea Association welcomes feedback from security researchers and the general public to help improve our security and the security of the tea Protocol. If you believe you have discovered a vulnerability, privacy issue, exposed data, or any other security issues in any of the tea Association’s assets, we want to hear from you. This document describes general best practices for reporting bugs and/or vulnerabilities.
VULNERABILITIES MUST NOT BE DISCLOSED PUBLICLY OR EXECUTED AGAINST THE PRODUCTION’S IMPLEMENTATION OF THE TEA PROTOCOL, WHETHER TESTNET OR MAINNET.
FAILURE TO COMPLY WITH THE ABOVE MAY BE PUTTING ALL USERS AT RISK AND WILL RESULT IN ANY AND ALL REWARDS BEING FORFEITED.
Systems in scope
All systems and web properties of the tea Association, including:
Website: https://tea.xyz
tea Protocol dashboard: https://app.tea.xyz
tea Protocol API endpoints
tea Protocol audited smart contracts
All code in the repositories of the following organization: https://github.com/teaxyz
Our Commitments
When working with us, according to this policy, you can expect us to:
Respond to your report promptly, and work with you to understand and validate the information included in your report;
Provide evidence when claiming that a bug/vulnerability report is known or duplicate;
Strive to keep you informed about the progress of a vulnerability as it is processed;
Work to remediate discovered vulnerabilities in a timely manner, within our operational constraints; and
Extend Safe Harbor for your vulnerability research that is related to this policy as set forth in this policy.
Our Expectations
In participating in our vulnerability disclosure program in good faith, we ask that you:
Follow the rules, including this policy and any other relevant agreements. If there is any inconsistency between this policy and any other applicable terms, the terms of this policy will prevail;
Report any vulnerability you’ve discovered
Promptly;
In English;
Without misrepresenting the asset (by claiming that a bug report impacts/targets an asset in scope when it does not) or the severity of the vulnerability;
Without disclosing the vulnerability publicly or to any other person, entity, or email address before the tea Association has been notified, has fixed the issue, and has granted permission in writing for public disclosure.
Are at least 18 years of age or, if younger, submit your vulnerability with the consent of your parent or guardian and otherwise meet all the eligibility requirements under to the Terms of Use;
Are not current or former employees, or a vendor or contractor who has been involved in the development of the code of the bug in question;
AI-generated/automated scanner bug reports will be ignored;
Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience;
Use only the Official Channels to discuss vulnerability information with us;
Provide us a reasonable amount of time (at least 180 days from the initial report) to resolve the issue before you disclose it publicly;
Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope;
If a vulnerability provides unintended access to data: Limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept; and cease testing and submit a report immediately if you encounter any user data during testing, such as Personally Identifiable Information (PII), Personal Healthcare Information (PHI), credit card data, or proprietary information;
Do not cause a denial of service on our platform through exploits, vulnerabilities, traffic, or causing issues with our technology providers;
Only interact with test accounts you own or with explicit permission from the account holder;
Do not use social engineering attacks, DDOS, physical access, spearfishing, etc. against the tea Association or any contributor to the tea Protocol or registered open-source projects;
Do not threaten, engage in extortion/blackmail or threaten to engage in extortion/blackmail;
Communicate professionally - Use of unprofessional language, harassment, excessive, abusive or bad faith communication will not be tolerated; and
Do not advertise/promote services, post illegal content, or impersonate other security researchers.
Official Channels
Please report security issues via this form, providing all relevant information. The more details you provide, the easier it will be for us to triage and fix the issue.
Safe Harbor
When conducting vulnerability research, according to this policy, we consider this research conducted under this policy to be:
Authorized concerning any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good-faith violations of this policy;
Authorized concerning any relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls;
Exempt from restrictions in our Terms of Use that would interfere with conducting security research, and we waive those restrictions on a limited basis; and
Lawful, helpful to the overall security of the Internet, and conducted in good faith.
You are expected, as always, to comply with all applicable laws. If legal action is initiated by a third party against you and you have complied with this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our Official Channels before going any further.
Note that the Safe Harbor applies only to legal claims under the control of the organization participating in this policy, and that the policy does not bind independent third parties.
Reporting Other Vulnerabilities
Vulnerabilities in any websites, email servers, or other non-critical infrastructure within the tea Protocol’s or tea Association stack can be reported directly to the tea Association via this form.
Last updated