Our promise to you

• We will respond to report in ultimately five working days, probably faster!
• We are happy to respond to any questions, please use the button in the right top corner for this.
• 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)
• 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 put our time in thanking researchers rather than blocking their IP's 😉)

InnoGames looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.

Focus Areas

Besides the classic web-based vulnerability classes such as XSS, CSRF, IDOR, SQLi, RCE, we are mostly interested in security vulnerabilities that affect the game's ecosystem in a negative manner, such as:

• Disclosure of personal information or messages from other player accounts
• Manipulation of the progress of other players
• Cheating in battles against other players

Out of scope domains

Everything which is not explicitly mentioned under "Targets" is currently out of scope. Additionally the following is out of scope:

• The contact form at https://www.innogames.com/company/contact/
• Brute-force testing is not allowed on login.innogames.de
• All newly, publicly released software vulnerabilities have a black out period of 30 days before they will be accepted in this program.
• All publicly released software vulnerabilities without a vendor fix or a mitigation by the vendor
• All of our other games
• All applications/services that are not InnoGames-branded or developed externally, for example:

*For .innogames.com (3rd party services, may not be tested):

• pn.innogames.com
• newsroom.innogames.com
• mail.innogames.com
• *.innogames.com domains which redirect you to a 3rd party service
• If in doubt a whois on the IP should show you if it is an external service or at least run by InnoGames

*For .innogames.com (3rd party applications, vulnerabilities due to outdated versions (>30d) or our custom settings are covered)

• forum.innogames.com

*For .innogames.de (3rd party services, may not be tested):

• slack.innogames.de
• surveys.innogames.de
• exchange.innogames.de
• mail.innogames.de
• om-cdn.innogames.de
• gamejam.innogames.de (which redirects to igjam.eu)
• *.innogames.de domains which redirect you to a 3rd party service
• If in doubt a whois on the IP should show you if it is an external service or at least run by InnoGames

*For .innogames.de (3rd party applications, vulnerabilities due to outdated versions (>30d) or our custom settings are covered):
This list contains subdomains of 3rd party applications, however there may be more which are not included, but still out of scope. Before submitting a report double-check if it is a system under InnoGames control.

• sip.innogames.de
• lyncdiscover.innogames.de
• mailout.innogames.de
• autodiscover.innogames.de
• email.*.innogames.de
• call.innogames.com
• sip.innogames.com
• conferencing.innogames.com
• mra.innogames.com
• meet.innogames.com
• jamf.innogames.com
• igjam.eu

All apps, which are not mentioned in the scope, are considered Out-Of-Scope, this also applies for their connected backend services, even though they might be on an in-scope server. If a specific route is solely used by the app, it will be considered as Out-Of-Scope

The following finding types are specifically excluded from the bounty:

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
• 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 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
• DMARC or SPF related issues
• All bugs that allow an individual to gain only personal (dis)advantages (no impact on other players)

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 30 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
• Using unreported vulnerabilities to find other bugs
• Internal pivoting, scanning, exploiting

Mobile

• Shared links leaked through the system clipboard
• Any URIs leaked because a malicious app has permission to view URIs opened
• The absence of certificate pinning
• Sensitive data in URLs/request bodies when protected by TLS
• Lack of obfuscation
• Path disclosure in the binary
• Lack of jailbreak & root detection
• Crashes due to malformed URL Schemes
• Lack of binary protection (anti-debugging) controls, mobile SSL pinning
• Snapshot/Pasteboard leakage
• Runtime hacking exploits (exploits only possible in a jailbroken environment)
• Certificates or static keys hard-coded/recoverable in apk/ipa API key used for insensitive activities/actions
• Attacks requiring physical access to the victim’s device
• Any kind of sensitive data stored in app private directory
• Any URIs leaked because a malicious app has permission to view URIs opened

Ratings and Rewards

For the initial prioritisation/rating of findings, this program will use the CVSS classifications. However, it is important to note that in some cases a vulnerability priority will be modified due to its likelihood or impact. In any instance where an issue is downgraded, a full, detailed explanation will be provided to the researcher - along with the opportunity to appeal, and make a case for a higher priority.

Exceptional

• RCE (Remote Code Execution)

Critical

• Access to restricted customer data (e.g. email address , personal messages)
• SQL injection

High

• Stored XSS without user interaction
• Account Takeover
• Authentication bypass on critical infrastructure

Medium

• XSS
• CSRF

Low

• Open redirect

Where can we get credentials for the app?

For the games: You can self-register on the application but please don’t forget to use your @intigriti.me address.
For the internal services/admin tools there will be no credentials. Consider this a black-box test.

Premium Testing Credit - Currency (Diamonds)

Feel free to create as many accounts as you need in order to efficiently test the game ecosystem. Every registered account will receive an amount of 250.000 diamonds in order to facilitate testing of the premium parts of the game. If you need more, just let us know.