Description

The national project “eHealth Hubs & MetaHub” coordinated by the eHealth platform is meant to make medical results from hospitals (and in the near future medical laboratories) available to any caregiver who currently is treating the patient . For detailed information see https://www.ehealth.fgov.be/nl/zorgverleners/online-diensten/hubs-metahub and the URL in the next paragraph. This system supplements the traditional system of addressed ‘email type’ communication to individual referrers. Before medical data about a patient can be shared, that patient has to grant the ‘eHealth informed consent’ (see http://www.patientconsent.be ). Further, care providers declare a therapeutic relationship with the patient. Communication between the hubs and between external physicians and a hub is according to the KMEHR standard: https://www.ehealth.fgov.be/standards/kmehr/content/page/web-services The scope of this project is confined to the hub exploited by VZNKUL (Vlaams Ziekenhuis Netwerk KU Leuven) implementation of this hub system. The central metahub hub from the Belgian government, the other hubs, and the systems at other partners of this project are out of scope.

Bounties
Low
Medium
High
Critical
Exceptional
Tier 2
€ 0
€ 100
€ 400
€ 1,250
€ 2,000
Up to € 2,000
Domains

hub.vznkul.be/*

Tier 2
URL

hub.vznkul.be/services/interhub/InterHubService

Tier 2
URL

hub.vznkul.be/services/intrahub/IntraHubService

Tier 2
URL

hubacc.vznkul.be/*

Tier 2
URL

hubacc.vznkul.be/services/acceptance/interhub/InterHubService

Tier 2
URL

hubacc.vznkul.be/services/acceptance/intrahub/IntraHubService

Tier 2
URL
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 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

  • 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

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

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

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

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)
FAQ

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.

All aboard!
Please log in or sign up 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 log in 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
Triage
Activity
6/15
UZ Leuven
closed a submission
6/15
UZ Leuven
closed a submission
6/12
logo
fvisvl0
created a submission
6/12
logo
fvisvl0
created a submission
5/12
UZ Leuven
closed a submission
5/12
UZ Leuven
closed a submission
5/11
logo
lucifer3560
created a submission
5/11
logo
0x48iffy
created a submission
5/2
UZ Leuven
closed a submission
5/1
logo
kamranjaved
created a submission