Intigriti
Description

Website + Android Apps + iOS Apps Android Apps KWS Companion The application is only to be used by doctors and no logon information will be given. mynexuz CPV The application is only to be used by personnel of UZ Leuven responsible for transport of patients and no logon information will be given. mynexuzhealth app This application is intended to be used by patients in order to consult their private data, their doctors & appointments and more. Login: see below. iOS Apps KWS Companion The application is only to be used by doctors and no logon information will be given. Website mynexuzhealth website This website is intended to be used by patients in order to consult their private data, their doctors & appointments and more. Login: see below. In order to be able to logon to the mynexuzhealth website and app, an ethical hacker will need to request one or more logon credentials via the platform. You can request this information via support (support@intigriti.be). The information they will receive is - A user ID of 8 numbers - A PIN code of 4 numbers - A QRCode

Bounties
Low
0.1 - 3.9
Medium
4.0 - 6.9
High
7.0 - 8.9
Critical
9.0 - 9.4
Exceptional
9.5 - 10.0
Tier 2
0
100
400
2,000
4,000
Tier 2
Up to €4,000
Rules of engagement
Not applicable
Not applicable
max. 5 requests/sec
Not applicable

Domains

134.58.179.82

Tier 2
Other
Tier 2
Android
Tier 2
Android
Tier 2
Android
Tier 2
URL

Registration for code cards used to authenticate on the mynexuzhealth application

Tier 2
URL
Tier 2
iOS
Tier 2
URL
Tier 2
URL

🇬🇧🇫🇷🇳🇱

Tier 2
URL

🇬🇧🇫🇷🇳🇱

Tier 2
iOS
Out of scope
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 of scope

Mynexuzhealthpro (for physicians) is out of scope

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

Mobile

  • Shared links leaked through the system clipboard
  • Any URIs leaked because a malicious app has permission to view URIs opened
  • The absence of certificate pinning
  • Sensitive data in URLs/request bodies when protected by TLS
  • Lack of obfuscation
  • Path disclosure in the binary
  • Lack of jailbreak & root detection
  • Crashes due to malformed URL Schemes
  • Lack of binary protection (anti-debugging) controls, mobile SSL pinning
  • Snapshot/Pasteboard leakage
  • Runtime hacking exploits (exploits only possible in a jailbroken environment)
  • API key leakage used for insensitive activities/actions
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.

Exceptional

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

Critical

  • Impersonation of other user (1 user per time)
  • Use other applications to view data of the patients
  • Reverse engineer app that grants you information to local data of patients

High

  • Service disruption (e.g. config change)

Medium

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

Where can I get credentials for the application?

In order to be able to logon to the mynexuzhealth website and app, you will need to request one or more logon credentials via the platform. You can request this information via support (support@intigriti.be). You will receive a PDF with all the info you need (like EAD number, password, and login codes). Make sure you copy the correct values over (or type them yourself), as copying from the PDF can be a bit finicky sometimes.

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.

Researchers
last contributors
logo
logo
logo
logo
logo
logo
leaderboard
logo
logo
logo
logo
logo
logo
Last 90 day response times
avg. time first response
< 3 days
avg. time to decide
< 2 weeks
avg. time to triage
< 3 days
Activity
7/10
UZ Leuven
closed a submission
7/8
logo
created a submission
5/27
UZ Leuven
closed a submission
5/27
UZ Leuven
closed a submission
5/27
UZ Leuven
closed a submission
5/27
UZ Leuven
closed a submission
5/27
UZ Leuven
closed a submission
5/27
UZ Leuven
closed a submission
5/27
UZ Leuven
closed a submission
5/23
UZ Leuven
closed a submission