Guidelines

• In addition some of our domains are in a shared environment and are subject to vendor Service Level Agreements with other parties. So please keep the amount of requests to an absolute required minimum to limit the impact on the shared environment.
• Please do NOT discuss bugs before they are fixed. You can send us a video as proof of concept, but remember to change its privacy settings to private or to secure the video with a password.

Reporting Guidelines

• Provide detailed but to-the point reproduction steps
• Include a clear attack scenario. How will this affect us exactly?
• Remember: quality over quantity!

Response timeframe

• We will respond to report in ultimately two weeks, probably faster!

Happy to learn about any vulnerability impacting our website but of course we are extra eager to learn the following:

• How the bad guys are scoring free tickets on our expense. Score yours in a good way!
• Changing our movie content/pictures! We don’t want to misinform our guests do we?
• Gather sensitive data about our clients, it’s more a thing between us and our client, you know?
• Do bad stuff with our business shop, we need to run a business as well!

We've listed all assets that you're allowed to test in the domains section.

Please use an intigriti.me for signups, this makes it easier for us to clean an overabundance of unused emails/accounts or to track and trace if something goes wrong!

Note: Log4j vulnerabilities are in scope of this program

While we happily welcome any input from researchers that showcases a potential vulnerability in one of our services, we have assembled a list of issues which are out of scope for this program. Exceptions can be made if the researcher provides a realistic attack scenario that showcases a significant risk to our security.

The following domains of Kinepolis including but not limited to:

• *.cineramabios.nl
• openx.kinepolis.com
• l.kinepolis.com
• dev.kinepolis.com
• jobs.kinepolis.com

Violations against best practices that only have a theoretical chance of exploitation such as:

• Lack of a strong password policy
• Lack of security headers (Unless the lack of a header is the direct cause of a vulnerability)
• Lack of rate limit on non-sensitive endpoints and/or bruteforce attacks
• Autocomplete functionality in forms
• Insignificant information disclosure
• Internal IP disclosure
• Descriptive error messages (Stack trace information, full path disclosure)
• Lack of the X-FRAME-OPTIONS header on static pages or pages that don’t contain dangerous or sensitive actions.
• Any form of DoS unless a *simple PoC showcases significant downtime
• Spamming
• User, and other insignificant, enumeration attacks
• Vulnerabilities as reported by automated tools without additional analysis as to how they're an issue in the context of our tool
• If all we receive is scanner output that turns out to be correct the submission will be accepted but no bounty will be awarded.
• Vulnerabilities that require extensive social engineering
• Social engineering of our employees/support
• Self-XSS
• XSS that is not exploitable in a modern browser
• Content injection if the only attack scenario is social engineering
• Issues that require your target to open the developer tools of a browser
• Issues that require an attacker to have physical access to the target’s device or network traffic.
• Weak SSL configurations and SSL/TLS scan reports (this means output from sites such as SSL Labs)
• Disclosure of used software and their version
• CSRF issues with low impact
• Sensitive information leaking to a trusted third party partner.
• 0 day vulnerabilities in software that haven’t been disclosed publicly for more than three months. We require time to schedule our updates to limit downtime on our systems and limit impact on user experience.
• Lack of the secure or HTTPOnly flag on cookies
• Publicly accessible login panels
• Open ports without an accompanying proof-of-concept demonstrating vulnerability
• The internal communications app "Kinetalks" is completely out of scope
• Issues regarding DMARC and DKIM, we have a project running in Proof of concept to fix this, as such all submissions regarding such vulnerabilities will immediatly be closed as out-scope. (this also includes reports about SPF records)
• public xmlrpc.php files
• Subdomain takeover without taking the subdomain over
• Pre-auth account takeover / oauth squatting
• API key disclosure without proven business impact

Out-scope for 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 is out of scope
• 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)
• API key leakage used for insensitive activities/actions (edited)

We are really happy with your support! To ensure you have a great feeling about your work for Kinepolis, we invite you and some friends in one of our theatres to have a great night, a look behind the scenes and enjoy the ultimate cinema experience even more intense!

While you are there, you might have the opportunity to check our cash machines! Create yourself a whole new cinema experience.

Please find some examples of criticalities below:

Exceptional

• Remote Code Execution

Critical

• SQL injection
• Access to all customer data

High

• Free tickets to catch a movie
• Impersonation of other user (1 user per time)
• Access to specific customer

Medium

• Public content manipulation (e.g. movie posters / movie trailer / movie description)

Low

• Scripting and automation
• Weak ciphers/certs
• Clickjacking
• XSS requiring extensive social engineering

Informative

• Debug stacktrace

Please also note that we rate our submissions based on business impact.

Where can we get credentials for the app?

You can self-register on the public URLs by clicking on the Sign In button. You will be redirected to with the option to register. Please do make use of your @intigriti.me email address.