By participating in this program, you agree to:

• Respect the Community Code of Conduct
• Respect the Intigriti Terms and Conditions
• Respect the scope of the program
• Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)

Validation times

We will validate all submissions within the below timelines, once your submission has been verified by Intigriti.
Submissions validated outside of this may be awarded a €50 bonus.

This remains at the discretion of Ziekenhuis Oost-Limburg to award.

Introduction

We are happy to announce our program! We've done our best to clean up our known issues and now would like to request your help to spot the ones we missed!

Our worst-case scenarios are:

We are particularly interested in vulnerabilities that could lead to significant impact.
Our "nightmare scenarios" include:

Data Breaches: Unauthorized access to sensitive member data or personal identifiable information (PII)
Privilege Escalation: Methods for a standard user to gain administrative rights or access restricted internal dashboards
Infrastructure Compromise: Remote Code Execution (RCE) on our servers or full takeover of our cloud environments
Disruption of Service: Serious logic flaws that could allow an attacker to bypass payment gateways or disrupt our core non-profit operations

Any useful infrastructure information:

This is a live Hospital environment. Take appropriate measures

Feedback
Would you like to help us improve our program or have some feedback to share, please send your anonymous feedback here:

Program feedback link
Please note this form will be checked periodically and should not be used for submission or support queries.

Domains

• Any domain that is not listed in the Domains section, is out of scope for this program

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
• Any CORS misconfiguration on speechreport.zol.be
• 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

This program follows Intigriti's triage standards based on the proof of concept.

Do you offer paid bounties?

Yes, but not through our VDP. If you would like to be considered for an invite to our private bug bounty, please submit a valid finding here so we can review your contribution and consider you for future invitations.

Where can we get credentials to participate?

We do not provide test credentials or "insider" access for our Vulnerability Disclosure Program. We encourage researchers to perform "black-box" testing—evaluating our systems from the perspective of an external party without prior knowledge or specialized access. This helps us identify the risks that a real-world attacker would encounter first.

Should I still report vulnerabilities related to the login process?

Absolutely. While we do not provide accounts, we are highly interested in any vulnerabilities that affect our authentication mechanisms. If you discover a way to bypass login screens, perform credential stuffing at scale, or exploit flaws in our "Forgot Password" or MFA flows, please let us know immediately.

Note

When testing login flows, please ensure you use non-existent "dummy" data. Under no circumstances should you attempt to access, modify, or interact with the accounts or data of other users.