Our promise to you

• We are happy to respond to any questions, please use the button in the right top corner to contact us
• We respect the safe harbour clause that you can find below

Your promise to us

• Provide detailed but to-the point reproduction steps
• Include a clear attack scenario. How will this affect us exactly?
• Remember: quality over quantity!
• Please do not discuss or post vulnerabilities without our consent (including PoC's on YouTube and Vimeo or any other service)
• Please do not use automatic scanners -be creative and do it yourself! We cannot accept any submissions found by using automatic scanners. Scanners also won't improve your skills, and can cause a high server load (we'd like to spend our time in thanking researchers rather than blocking their IP's 😉)

Sqills is pleased to announce our public bug bounty program! We've done our best to resolve most of our known issues and now would like to request your help to find the ones we may have missed! We are specifically looking for:

• vulnerabilties that lead to modification of content on the corporate website
• vulnerabilities that provide access to the management system or server that hosts the corporate website
• vulnerabilities found on management systems that are hosted on *.sqills.com. These systems (e.g. Jenkins, Nexus) should not be publicly available.
• applications hosted on *.cloud.sqills.com that are part of another (invite-only) program that has bounties enabled. A finding on this domain may be reported through this program as well. When a report meets the requirements, we will invite you to the bounty program and a bounty will be awarded.

We plan to review our scope each month so make sure to visit regularly or subscribe to our program to receive updates when we make them!

Feedback
Would you like to help us improve our program or have some feedback to share, please send your anonymous feedback here:
Program Feedback Link
Please note this form will be checked periodically and should not be used for submission or support queries.

Out of scope domains

• booking.*.sqills.com
• *-prod.cloud.sqills.com
• booking.*.cloud.sqills.com
• careers.sqills.com
• *.red.sqills.team

Application

• Leaked tickets on ticket.*.cloud.sqills.com (we're already aware of this and working on a fix)
• API key disclosure without proven business impact
• Wordpress usernames disclosure
• Pre-Auth Account takeover/OAuth squatting
• Self-XSS that cannot be used to exploit other users
• Verbose messages/files/directory listings without disclosing any sensitive information
• CORS misconfiguration on non-sensitive endpoints
• Missing cookie flags
• Missing security headers
• Cross-site Request Forgery with no or low impact
• Presence of autocomplete attribute on web forms
• Reverse tabnabbing
• Bypassing rate-limits or the non-existence of rate-limits.
• Best practices violations (password complexity, expiration, re-use, etc.)
• Clickjacking without proven impact/unrealistic user interaction
• CSV Injection
• Sessions not being invalidated (logout, enabling 2FA, etc.)
• Tokens leaked to third parties
• Anything related to email spoofing, SPF, DMARC or DKIM
• Content injection without being able to modify the HTML
• Username/email enumeration
• Email bombing
• HTTP Request smuggling without any proven impact
• Homograph attacks
• XMLRPC enabled
• Banner grabbing/Version disclosure
• Not stripping metadata of files
• Same-site scripting
• Subdomain takeover without taking over the subdomain
• Arbitrary file upload without proof of the existence of the uploaded file
• Blind SSRF without proven business impact (pingbacks are not sufficient)
• Disclosed/misconfigured Google Maps API keys
• Host header injection without proven business impact

General

• In case that a reported vulnerability was already known to the company from their own tests, it will be flagged as a duplicate
• Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited
• Spam, social engineering and physical intrusion
• DoS/DDoS attacks or brute force attacks
• Vulnerabilities that only work on software that no longer receive security updates
• Attacks requiring physical access to a victim's computer/device, man in the middle or compromised user accounts
• Recently discovered zero-day vulnerabilities found in in-scope assets within 14 days after the public release of a patch or mitigation may be reported, but are usually not eligible for a bounty
• Reports that state that software is out of date/vulnerable without a proof-of-concept

This program follows Intigriti’s contextual CVSS standard.

Where can we get credentials for the app?

We currently don’t offer any credentials to test user roles.