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

Application

• Wordpress usernames disclosure
• Pre-Auth Account takeover/OAuth squatting
• Self-XSS that can't 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 aren't 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

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.