The Domains listed in the project description are purely informational, and are not in scope.

• https://www.ehealth.fgov.be
• http://www.patientconsent.be

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 link to OTHER hubs or the central meta-hub are out of scope!
The Belgian government and the eHealth platform do not participate in this project.
If in doubt, please contact us before proceeding to test further systems.

www.vznkul.be is out of 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:

Application

• API key disclosure without proven business impact
• Wordpress usernames disclosure
• 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 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 are not 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

Bounties

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
• circumvention of access rules at the Intra-hub (see FAQ)

High

• Service disruption (e.g. config change)

Medium

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

How does this work?
There are 2 separate services to the HUB:

• Intra-Hub located at https://hub.vznkul.be/services/intrahub/IntraHubService
  Used by other hospitals/general physisians/etc. To access a patient record, some criteria have to be met:

  1. Patient needs to have given his/her conformed insent
  2. Patient needs to have a therapeutic relationship with the requester of the Record
  3. Patient can exclude specific physicians from his/her Patient Record, Physician cannot be on this "blocklist"

• Inter-hub located at https://hub.vznkul.be/services/interhub/InterHubService
  Used by other HUBs. Once granted access, no other checking on specific record is performed. It is the task of the HUB partner to check if the original requester is permitted to access.

Where can I get credentials to login?
At this time, we cannot provide a valid certificate to login yet. Use your creativity to find exploits.