Waitwhile Bug Bounty Program
Waitwhile is committed to security and protecting our customers’ data. As part of this, we encourage security researchers to put our security to the test - and we offer a variety of rewards for doing so. We look forward to continuing to work with the community as we add new features and services.
This page is intended for security researchers. For general information about security at Waitwhile, please see our Security program.
- Automated testing is not permitted.
- Test only with your own account(s) when investigating bugs, and do not interact with other accounts without the consent of their owners.
- You must be the first person to report the issue to us. We will review duplicate bugs to see if they provide additional information, but otherwise only reward the first reporter.
- We award bounties at time of fix, and will keep you posted as we work to resolve them.
- Report identified bugs to firstname.lastname@example.org
Bug Bounty Rewards
The following guidelines give you an idea of what we usually pay out for different classes of bugs. Low-quality reports may be rewarded below these tiers, so please make sure that there is enough information for us to be able to reproduce your issue. Step-by-step instructions including how to reproduce your issue starting out by creating a fresh Waitwhile account are preferred. Screenshots and videos are also helpful, but please make sure to not make these public before submitting them to follow our program’s rules.
There is no maximum reward - particularly creative or severe bugs will be rewarded accordingly. Depending on the severity of the bug, and the quality of your report, we may pay a lower-tier bug out at a higher level.
Tier 3: Low Severity Bugs $25 and up
- Mixed content issues
- "Tab-Nabbing" or other rel="noopener" bugs
- Self-XSS (XSS requiring interaction other than browsing to exploit)
- Server misconfiguration or provisioning errors
- And other low-severity issues
Tier 2: Medium Severity Bugs $50 and up
- Cross-Site Request Forgery on Sensitive Actions or Functions (CSRF/XSRF)
- Broken Authentication affecting a single account
- Privilege Escalation affecting a single account
- SSRF to an internal service, hosted by Waitwhile
- Information leaks or disclosure (including customer data)
- And other medium-severity issues
Tier 1: High Severity Bugs $150 and up
- Information leaks or disclosure of customer data
Tier 0: Critical Severity Bugs $250 and up
- SQL Injection
- Remote Code Execution
- Privilege Escalation affecting all accounts
- Broken Authentication affecting all accounts
- SSRF to an internal service, with extremely critical impact (e.g. immediate and direct security risk)
- And other critical-severity issues
What’s In Scope
The following bugs are unlikely to be eligible for a bounty:
- Issues found through automated testing
- "Scanner output" or scanner-generated reports
- Publicly-released bugs in internet software within 3 days of their disclosure
- "Advisory" or "Informational" reports that do not include any Waitwhile-specific testing or context
- Vulnerabilities requiring physical access to the victim's unlocked device
- Denial of Service attacks
- Brute Force attacks
- Spam or Social Engineering techniques, including:
- SPF and DKIM issues
- Content injection
- Hyperlink injection in emails
- IDN homograph attacks
- RTL Ambiguity
- Content Spoofing
- Issues relating to Password Policy
- Full-Path Disclosure on any property
- Version number information disclosure
- Clickjacking on pre-authenticated pages, or the non-existence of X-Frame-Options, or other non-exploitable clickjacking issues (An exploitable clickjacking vulnerability requires a) a frame-able page that is b) used by an authenticated user and c) which has a state-changing action on it vulnerable to clickjacking/frame re-dressing)
- CSRF-able actions that do not require authentication (or a session) to exploit
- Reports related to the following security-related headers:
- Strict Transport Security (HSTS)
- XSS mitigation headers (X-Content-Type and X-XSS-Protection)
- Content Security Policy (CSP) settings (excluding nosniff in an exploitable scenario)
- Bugs that do not represent any security risk - these should be reported to email@example.com.
- Security bugs in help.waitwhile.com - this site runs on Intercom, so if you find vulnerabilities in the Intercom service, please see Intercom's bounty program for reporting details
- Security bugs in third-party applications or services built on the Waitwhile API - please report them to the third party that built the application or service
- Submissions from former Waitwhile employees within one year of their departure from Waitwhile
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.