Bug Bounty Form

You're about to submit a report to Loom. Provide as much information as possible about the potential issue you have discovered. The more information you provide, the quicker Loom will be able to validate the issue.

Responsible Disclosure Policy

  1. Please provide us with a reasonable amount of time to resolve the issue before disclosing it to the public or a third party.
  2. Follow HackerOne's disclosure guidelines.

Program Rules 

  1. 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.
  2. Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  3. When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
  4. Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
  5. Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  6. 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 explicit permission of the account holder.
  7. Please refrain from using any brute-forcing or dynamic scanning tools that will cause harm to Loom. DoS and brute-forcing our endpoints are out of scope.


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

  1. Clickjacking on pages with no sensitive actions
  2. Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
  3. Attacks requiring MITM or physical access to a user's device.
  4. Previously known vulnerable libraries without a working Proof of Concept.
  5. Comma Separated Values (CSV) injection without demonstrating a vulnerability.
  6. Missing best practices in SSL/TLS configuration.
  7. Any activity that could lead to the disruption of our service (DoS).
  8. Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
  9. Attempting to compromise our endpoints by brute forcing.
  10. Missing best practices in Content Security Policy.
  11. Missing HttpOnly or Secure flags on cookies
  12. Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
  13. Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
  14. Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
  15. Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.
  16. Tabnabbing
  17. Open redirect - unless an additional security impact can be demonstrated
  18. Issues that require unlikely user interaction

Was this article helpful?
0 out of 1 found this helpful