Your testing should be kid-safe, ethical, legal and fun!

Thank you in advance for your help in keeping Jooki fun, safe and reliable for kids.
--Team Muuselabs

• my.jooki.rocks - the web app and backend server
• *.jooki.rocks - any other service hosted by Muuselabs excluding our web stores (see Out Scope)
• *.muuselabs.com - company website and associated services

We're a small Belgian startup scrambling to scale, so we want to limit the impact of testing on staff time. The following are out of scope for now:

• DoS attacks
• Social engineering
• www.jooki.rocks - our web store
• ca|en|eu|fr|nl|uk|us.jooki.rocks - our international web stores
• Our listings & reviews on 3rd party web stores (Amazon, Bol, etc)
• Muuselabs accounts on 3rd party sites: social media, github, G Suite etc.

We plan to expand the scope of this project later as these could be fun ;-)

Application

• 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 on pages with no sensitive actions
• CSV Injection
• Host header injection without proven business impact
• Blind SSRF without proven business impact (DNS pingback only is not sufficient)
• Disclosed and/or misconfigured Google API key (including maps)
• Sessions not being invalidated (logout, enabling 2FA, ..)
• Hyperlink injection/takeovers
• Mixed content type issues
• Cross-domain referer leakage
• Anything related to email spoofing, SPF, DMARC or DKIM
• Content injection
• Username / email enumeration
• E-mail bombing
• HTTP Request smuggling without any proven impact
• Homograph attacks
• XMLRPC enabled
• Banner grabbing / Version disclosure
• Open ports without an accompanying proof-of-concept demonstrating vulnerability
• Weak SSL configurations and SSL/TLS scan reports
• Not stripping metadata of images
• Disclosing credentials without proven impact
• Disclosing API keys without proven impact
• Same-site scripting
• Subdomain takeover without taken over the subdomain
• Arbitrary file upload without proof of the existence of the uploaded file

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, may be excluded or be lowered in severity
• Spam, social engineering and physical intrusion
• DoS/DDoS attacks or brute force attacks.
• Vulnerabilities that are limited to non-current browsers (older than 3 versions) will not be accepted
• 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

At the moment there are no cash bounties for this project. However, high, critical and exceptional exploits will be rewarded with a Jooki 2 (when they start shipping).

All our rewards are impact based, therefore we kindly ask you to carefully evaluate a vulnerability's impact when picking a severity rating. To give you an idea of what kind of bugs belong in a certain severity rating we've put some examples below. Note that depending on the impact a bug can sometimes be given a higher/lower severity rating.

Examples of these levels include:

Critical:

• Remote Code Execution on a Muuselabs server with the potential to take control of all Jooki

High:

• Exploits with potential to access private customer data
• Exploits with potential to expose business-critical Muuselabs Intellectual Property

Medium:

• Exploits with a potential to harm the integrity of the Muuselabs assets and its customers, such as stored XSS on a public page.