Tier 2
€ 0
€ 100
€ 400
€ 850
€ 1,000
Up to € 1,000

Tier 2

Tier 2
IP Range

Tier 2
IP Range

Tier 2

This website is used to provide patient access to their radiology images (PACS). Patients logon with their date of birth, and a unique code provided to them by the physician. This code provides access to one study.

In scope

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
Out scope

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:


  • 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 on non sensitive cookies
  • Missing security headers which do not present an immediate security vulnerability
  • 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 without sensitive actions
  • CSV Injection
  • Host Header Injection
  • 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


  • 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 the usage of shared computers, man in the middle or compromised user accounts
  • Recently disclosed zero-day vulnerabilities in commercial products where no patch or a recent patch (< 2 weeks) is available. We need time to patch our systems just like everyone else - please give us 2 weeks before reporting these types of issues.
  • Attacks requiring unrealistic user interaction
Rules of engagement

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.

Safe harbour for researchers

UZ Leuven considers ethical hacking activities conducted consistent with the Researcher Guidelines, the Program description and restrictions (the Terms) to constitute “authorized” conduct under criminal law. UZ Leuven will not pursue civil action or initiate a complaint for accidental, good faith violations, nor will they file a complaint for circumventing technological measures used by us to protect the scope as part of your ethical hacking activities.

If legal action is initiated by a third party against you and you have complied with the Terms, UZ Leuven will take steps to make it known that your actions were conducted in compliance and with our approval.

Severity assessment

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.


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


  • Access to random patient record


  • Service disruption (e.g. config change)


  • 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!

All aboard!
Please login or register on the platform

For obvious reasons we can only allow submissions or applications for our program with a valid intigriti account.

It will only take 2 minutes to create a new one or even less to login with an existing account, so don't hesitate and let's get started. We would be thrilled to have you as part of our community.

Program specifics
ID check required
Reputation points
UZ Leuven
closed a submission
created a submission
UZ Leuven
closed a submission
created a submission
UZ Leuven
closed a submission
UZ Leuven
accepted a submission
UZ Leuven
closed a submission
created a submission
UZ Leuven
changed the out scope
UZ Leuven
changed the faq