DailyBot Security
Bug Bounty

Welcome to our Security Bug Bounty

At DailyBot, we take privacy and security very seriously. As such, we encourage everyone to participate in our open bug bounty program, which incentivizes researchers and hackers alike to responsibly find, disclose, and help us resolve security vulnerabilities. As with many bug bounties out there, DailyBot has a fairly straightforward and simple set of rules that help protect both us and those looking to disclose. Thanks for participating and happy bug hunting!

How we approach security issues

  • DailyBot will not take legal action against users for disclosing vulnerabilities as instructed here.
  • Vulnerability reports will always be responded to as fast as possible—usually within 24 hours.
  • We will provide a full write-up of steps we've taken to resolve any issues you reported.
  • Based on the validity, severity, and scope of each issue, we'll reward you with awesome stuff (or just cold, hard cash if you prefer).

Program Rules

  • Only use and test on accounts and servers you directly own. Testing should never affect other users.
  • Testing should be limited to sites and services that DailyBot directly operates. We will not accept reports for third-party services or providers that integrate with DailyBot through our APIs.
  • Don't perform any actions that could harm the reliability or integrity of our services and data. Some examples of harmful activities that are not permitted under this bounty include: brute forcing, denial of service (DoS), spamming, timing attacks, etc.
  • Don't use scanners or automated tools to find vulnerabilities.
  • Don't try to test API Rate Limits neither make a high amount of requests under a short period of time.
  • No information about issues found should be publicly disclosed or shared until we've completed our investigation and resolution. After confirmation, you are free to document and publish any information about the issues you've found.

Out of Scope Vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are generally considered out of scope (not an exhaustive list):
  • Account/E-mail enumeration
  • Attacks requiring MITM or physical access to a user's device
  • Brute force attacks
  • API Rate Limits
  • Clickjacking
  • Content spoofing and text injection
  • CSRF vulnerabilities
  • Denial of Service attacks
  • Email SPF, DKIM, and DMARC records
  • Invite enumeration
  • Missing HttpOnly/Secure cookie flags
  • Open CORS headers
  • Publicly accessible login panels
  • Reports from scanners and automated tools
  • Reports out of the subdomains app.dailybot.com, api.dailybot.co, and api.dailybot.com
  • Self-exploitation (like token reuse and console scripting)
  • Social engineering or phishing attacks targeting users or staff
  • Vulnerabilities related to other systems (i.e. help.dailybot.com) which is a Zendesk app

Found a bug already?