Agoric believes that strong security requires collaboration with skilled security researchers to improve the resilience of our code and its capabilities. We encourage you to notify us if you believe you've found a security issue in our source code or smart contracts.

Coordinated Disclosure with Agoric

• Bugs in the Agoric SDK can be reported to the Agoric HackerOne program or [email protected] .

  • Bugs submitted to HackerOne that are within the scope of the program may be eligible for a reward.

• It is essential to be able to provide steps that reproduce the issue and demonstrate its impact with a Proof of Concept example in an initial bug report. Before reporting a bug, a reporter may want to have another trusted individual reproduce the issue.

• A bug reporter can expect acknowledgment of a potential vulnerability reported through HackerOne or [email protected] within 5 business days of submitting a report. Please reach out again if an issue is not acknowledged within this time frame.

• For the safety and security of the network, bug reporters should not publicly share the details of a security bug on Twitter, Discord, Telegram, or in public Github issues during the coordination process.

• Once a vulnerability report has been received and triaged:

  • Agoric maintainers will confirm whether it is valid and will provide updates to the reporter.
  • It may take up to 10 business days to validate an issue.

• When the Agoric team has verified an issue, remediation steps and patch release timeline information will be shared with the reporter.

  • Complexity, severity, impact, and likelihood of exploitation are all vital factors determining the amount of time required to remediate an issue and distribute a fix.
  • If an issue is of Critical or High Severity, Agoric maintainers will release a security advisory to notify impacted parties and prepare for an emergency fix.
  • While the current industry standard for vulnerability coordination resolution is 90 days, Agoric code maintainers will strive to release a patch as quickly as possible.

When a bug patch is included in a software release, the Agoric code maintainers will:

• Confirm the version and date of the software release with the reporter.
• Provide information about the security issue that the software release resolves.
• Credit the bug reporter for discovery by adding thanks in release notes, securing a CVE designation if applicable.

Program Rewards

• Rewards are based on severity per CVSS (the Common Vulnerability Scoring Standard)
• All bounty amounts will be at the discretion of the Agoric team.
• Reports submitted using methods that violate policy rules will not be eligible for a reward.
• The report must be for in-scope assets to be eligible for a reward.
• Multiple reports describing the same vulnerability against multiple assets or endpoints with the same root cause will be treated as one report.
• While we aim for consistency, previous reports and prior bounty amounts will not set a precedent for future report eligibility or severity.
• Understand that there could be submissions for which we accept the risk, have other compensating controls, or will not address in the manner expected. When this happens, we will act as transparently as possible to provide you with the necessary context regarding how the decision was made.

Program Rules + Eligibility

This program does not cover algorithmic websites, web applications, or mobile applications. It also does not cover Agoric corporate assets such as Zoom, Slack, Google Suite, etc.

• You agree and adhere to the Program Rules and Legal terms stated in this policy.
• You are the first to submit a sufficiently reproducible report for a vulnerability to be eligible for the report to be accepted.
• You are available to supply additional information as needed by our team to reproduce and triage the issue.
• Publicly known zero-day vulnerabilities will not be considered for eligibility until more than 30 days have passed since patch availability.
• Out-of-scope vulnerability reports or reports that are technically reproducible but pose a very low security impact are likely to be closed as Informative.
• Agoric employees and third-party assets employees are not eligible for participation in this program.

Do:

• Read and abide by the program policy.
• Perform testing using only your accounts.
• Exercise caution when testing to avoid negative impact to customers and the services they depend on.
• STOP testing if you are unsure about its impact on our systems. If you think you may cause, or have caused, damage with testing a vulnerability, report your initial finding(s) and request authorization to continue testing.

Do not:

• Do not brute force credentials or guess credentials to gain access to systems.
• Do not participate in denial of service attacks.
• Do not upload shells or create a backdoor of any kind.
• Do not engage in any form of social engineering of Agoric employees, customers, or vendors.
• Do not engage or target any Agoric employee, customer, or vendor during your testing.
• Do not attempt to extract, download, or otherwise exfiltrate data that you believe may have PII or other sensitive data other than your own.
• Do not change passwords of any account that is not yours or that you do not have explicit permission to change. If ever prompted to change an account password you did not register yourself or an account that was not provided to you, stop and report the finding immediately.
• Do not do anything that would be considered a privacy violation, cause destruction of data, or interrupt or degrade our service. Do not interact with accounts you do not own or without the explicit permission of the account holder.

You may not discuss this program or any vulnerabilities (even invalid and resolved ones) outside of the program without express consent from the organization. If you are interested in sharing any information about your testing methodology related to an Agoric report, you must request permission on your report, and you must receive written approval from an Agoric team member. Generally, we will strive to support the sharing of research and share information about issues reported to our program.

Scope

Please consult the list below on this page, under "Scopes" for a complete list of bounty-eligible targets.

Out of Scope

Reports that include these issues will be considered out of scope and, therefore, are ineligible for bounty. Please refrain from submitting issues that fall into the following categories, as doing so may negatively impact your reputation score.

• Social engineering and physical attacks of any kind
• Security issues in dependencies of project without a proof-of-concept demonstrating exploitability with the applied use case of that dependency as used by the project in scope
• Information leakage that cannot be used to make a direct attack, like server IP, server version, path, error message, internal IP, etc.
• Reports from automated tools or scans.
• Dependency confusion
• Distributed Denial of Service attacks that require large volumes of data.
• Zero-day vulnerabilities less than 30 days from patch release
• Security vulnerabilities in third-party products or websites not controlled by Agoric.
• "Self" XSS
• Session fixation
• Content Spoofing
• Missing cookie flags
• SSL/TLS best practices
• Mixed content warnings
• Clickjacking, tabnabbing, and UI redressing
• Reflected file download attacks (RFD)
• Feedback, comment, message, SMS, email, etc. flooding
• Login, logout, unauthenticated, or low-impact CSRF
• All spam-related email configuration, including SPF, DMARC, DKIM
• Attacks requiring man-in-the-middle (MITM)
• Issues related to networking protocols or industry standards
• Error information disclosure that cannot be used to make a direct attack
• Missing security-related HTTP headers that do not lead directly to a vulnerability
• Any issues related to the distribution of software.

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 a third party against you initiates legal action 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 our company and our users safe!