Kahootz Vulnerability Disclosure and Reporting

Safeguarding Collaboration Together

As a leading software-as-a-service collaboration platform, we are committed to providing our users with a safe and secure environment. We understand that vulnerabilities can affect any system, including our public-facing website. That’s why we actively encourage security researchers, ethical hackers, and our users to report any potential security flaws they discover. Your valuable contributions help us maintain the highest standards of data protection.

Responsible Vulnerability Disclosure at Kahootz

Our dedicated security team is here to address potential vulnerabilities responsibly. We highly value the time and effort of security researchers, and we follow a strict, Responsible Disclosure Policy to ensure a collaborative and transparent approach to handling reported vulnerabilities.

Why Report Vulnerabilities to Kahootz?

By disclosing vulnerabilities to us, you contribute to our platform’s security and play a crucial role in safeguarding the data of thousands of users who rely on Kahootz for seamless collaboration. Your partnership in this endeavour can make a significant impact and protect sensitive information from potential exploits.

Responsible Disclosure Process at a Glance:

• Prompt Acknowledgment: Expect a quick acknowledgement of your report upon submission. We aim for our first response in two working days and triage within the next two days.
• Transparent Communication: We will let you know about the progress of your report and any steps taken to address the issue.
• Collaborative Approach: Our security team will work closely with you to understand and validate the vulnerability.
• No Public Disclosure: Please do not discuss any vulnerabilities (even resolved ones) with other people without our express consent.  Please follow HackerOne’s disclosure guidelines.
• Legal Protection (Safe Harbour): You can trust that we will not pursue legal action against security researchers who follow responsible disclosure practices.

How to Report a Vulnerability:

Help us maintain a safe and secure collaboration platform by reporting potential vulnerabilities to our security team.

Please review our guidelines below and submit your response .

Programme rules

1. Please provide detailed reports (in English) with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged.
2. Submit one vulnerability per report unless you need to chain vulnerabilities to provide impact.
3. When duplicates occur, we only triage the first report received (provided that it can be fully reproduced).
4. Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.
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 the explicit permission of the account holder.

General Advice

• In order to identify vulnerabilities and confirm them, you may find it useful to create your own Kahootz site.  You can do this from kahootz.com
• If you make too many requests to the Kahootz site in a short space of time, your IP will be automatically blocked from the service.
• This is not a Bug Bounty Programme!

Out-of-Scope Vulnerabilities

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

• Clickjacking on pages with no sensitive actions
• Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
• Attacks requiring MITM or physical access to a user’s device.
• Previously known vulnerable libraries without a working Proof of Concept.
• Comma Separated Values (CSV) injection without demonstrating a vulnerability.
• Missing best practices in SSL/TLS configuration.
• Any activity that could lead to the disruption of our service (DoS).
• Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
• Rate limiting or bruteforce issues on non-authentication endpoints
• Missing best practices in Content Security Policy.
• Missing HttpOnly or Secure flags on cookies
• Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
• Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
• Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
• Tabnabbing
• Open redirect – unless an additional security impact can be demonstrated
• Issues that require unlikely user interaction
• Stored XSS or other issues in the “Applet” dashboard item

Let’s Build a Safer Future Together

At Kahootz, we believe a united effort ensures a safer future for everyone. Join us in this vital mission to protect our platform and user data from potential threats. Together, we can continue to provide a worry-free collaboration experience on Kahootz. Thank you for your partnership in safeguarding collaboration and strengthening our security measures.