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)

We Are Specifically Looking For

• Accessing any user, customer, or partner sensitive information
• PHI (Protected Health Information) and PII (Personally Identifiable Information)
• Remote Code Execution vulnerabilities are also on our target

OpenAPI Documents

• Assessment BFF Open Api documentation is added as attachment.

Extra Information

• For FHIR and Smart Auth flows, please check the related repositories https://github.com/adahealth
• Some endpoints can host OpenApi and GraphQL documentation
• We have stage endpoints without real data corresponding to prod environment. 20 reqs/sec are accepted on stage environments. Reconnaissance techniques can be applied for discovering. Found vulnerabilities for listed assets will be accepted.

SLA Internally

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 €25 bonus. This remains at the discretion of Ada Health to award.

Working hours = Mon - Fri 9 AM - 5 PM CET

Check Our Fix

We may offer up to €50 bonus to verify a resolved High, Critical, or Exceptional issue. This remains at the discretion of Ada Health to award.

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.

Out-of-Scope Domains

• *.httpproxy.data.ada.com
• monitoring.*.enterprise.ada.com
• monitoring.*.gcp.ada.com
• monitoring.*.enterprise.adahahealth.ca
• monitoring.*.gcp.adahealth.ca

Out-of-Scope Topics

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

Web Application

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

Mobile Application

• 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

Known Issues & Accepted Risks

• Account takeover via deep link (ada://mobile-social-login) hijacking in Android app
• Bypassing the Ada-BFF Consumer API (Mobile App interacts with) Request Limit (HTTP "x-ratelimit-limit"header) via XFF Header on
• OAuth configuration issues.
• Randomly generated assessment and session identities for unauthenticated flows

This program follows Intigriti's contextual CVSS standard

Where can we get credentials for the mobile app?

You can self-register on the application but please don’t forget to use your @intigriti.me address.

Are domains which interact directly with the in-scope endpoints also considered to be in-scope?

Nope, only the listed assets are in the scope currently.