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)

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:

ADAC represents trust, reliability, and security.

In a worst-case scenario, a critical vulnerability could lead to a large-scale breach of customer and insurance data, including highly sensitive medical information.
Such an incident could severely damage trust, trigger regulatory consequences, and expose customers to significant risk. At the same time, compromised availability or integrity of core systems for service delivery and claims processing could disrupt essential operations. Preventing data leakage and ensuring continuous, reliable operations is therefore of highest priority.

Any useful infrastructure information:

The in-scope environment is based on a hybrid infrastructure model, combining both internally operated systems and services hosted by cloud providers.

ADAC Specific

• Basic availability of digital services
• Scanner-generated reports without concrete vulnerability references
• Descriptive error messages / stack traces / application or server errors
• Fingerprinting / banner disclosure on common/public services (broader than just version disclosure/banner grabbing)
• Logout CSRF
• Content Spoofing
• Weak Captcha / Captcha bypass
• Login or Forgot Password brute force / missing account lockout
• HTTP/DNS cache poisoning
• SSL/TLS issues (BEAST, BREACH, weak ciphers, lack of forward secrecy, etc.)
• XSS requiring local access / User-Agent injection
• Vulnerabilities limited to unsupported browsers
• Known vulnerable/outdated third-party libraries without proven exploitability
• Source code disclosure vulnerabilities
• Information disclosure of non-confidential information
• Ability to upload/download viruses or malicious files
• Request Flooding

Application

• Wordpress usernames disclosure
• Pre-Auth Account takeover/OAuth squatting
• Self-XSS that can't 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 aren't 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

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

Where can we get credentials for the app?

Please register individual accounts for your investigations using your intigriti.me email address. Stop testing if you encounter any payment details to be added.