By participating in this program, you agree to:

• For the IDM scope, you can only request a test account with your intigriti.me e-mail account
• Respect the Community Code of Conduct
• Respect the Terms and Conditions
• Respect the scope of the program
• Not discuss or disclose vulnerability information without prior written consent, including PoC's on public Youtube or Vimeo channels.
• We appreciate a video PoC in case of complicated vulnerabilities.

We've done our best to clean most of our known issues and now would like to request your help to spot the ones we missed! We are specifically looking for

• Leaking of personal data
• Horizontal / vertical privilege escalation
• SQL injection vulnerabilities
• Arbitrary file upload (proof of the existence of the uploaded file required)
• Sessions not being invalidated (upon logout, enabling 2FA)
• Hyperlink injection/takeovers
• Cross-domain referer leakage
• Username / email enumeration (for internal e-mail accounts)

Subdomain Takeover
If a certain subdomain seems to be vulnerable to subdomain takeover, we want to know this but we ask to not take over the corresponding subdomain itself. Make sure you give a proper explanation on how to take this over and which service is responsible for this.

Other

• Any domain that is not listed in the Domains section, is out of scope for this program (non-exhaustive list of out of scope domains)
• Third party services are out of scope (only misconfigurations are in scope)
• You can login, but the authentication flow is not in scope of this domain.

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
• Tokens leaked to third parties
• Anything related to email spoofing, SPF, DMARC or DKIM
• Content injection without being able to modify the HTML
• 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
• 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

Where can we get credentials for the app?
You can log on via https://burgerprofiel.beta-vlaanderen.be by clicking on "Meld u aan". This will redirect you to https://beta.openid.burgerprofiel.dev-vlaanderen.be/ . Here you need to select an INSZ (= the account) and click on "Login". Multiple testing accounts are available.

Will you get recognition for relaying vulnerabilities?
We will create a section on our website, where we can mention your name or alias and the number of vulnerabilities you relayed to us.