For this project, we are bound to 3rd-party closed-source software for some parts.
Please be aware that we will not be able to fix all bugs internally, and may have to await other vendors.

We are particularly interested, but not limited to, find out how one can exploit our system to:

• Horizontal or vertical privilege escalation
• XSS (no self-xss and only on latest versions of browsers)
• RCE
• SQL injection
• …

Any area that is not explicitly listed in the section above is out of scope. The areas that are out of scope include, but are not limited to, the following:

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

It will be the responsibility of intigriti to pay ethical hackers in a timely and legal way. Payouts will only take place after agreement with UZ Leuven on the criticality of the impact and only if the submission was the first of its kind and agreed to be valid.

Duplicates policy: When two identical issues are reported, with different endpoints being the only difference between submissions, only the first submission will have the criticality below assigned.
If similar reports by the same user are reported within 14 days after accepting the previous (only differentiating in endpoint), the reports will be accepted but in a lower criticality and hence impact the bounty.

Rewards in this project are categorised according to impact, not according to attack vector.

Exceptional

• Remote Code Execution
• Access to all patient records
• Access to specific patient record

Critical

• Access to random patient record

High

• Service disruption (e.g. config change)

Medium

• Compomise of one user, with user interaction required (Reflective XSS)

Can we use test accounts?

The following login data can be used to test the platform.

• Patient 1:
  Code: e3Dgin2r
  D.o.B: 05/09/1967

• Patient 2:
  Code: mcuk7jp4
  D.o.B: 01/05/1967

Please do not DDOS these logins and don’t try to guess other codes, ... . The usernames will automatically be locked!