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 €25 bonus.

This remains at the discretion of Dstny to award.

Check our fix
We offer up to €50 bonus to verify a resolved issue for us (when requested by Dstny).
This remains at the discretion of Dstny to award.

Our worst-case scenario is losing customer trust by:

• experiencing a data leak that could have been avoided by applying technical and organizational best practices.
• suffering a major outage due to an intrusion of a threat actor in our applications, systems or network.

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 specifically listed in the Domains section, is out of scope for this program.

• Application redirects (HTTP/HTTPS/...) from a in-scope domain to a domain out of scope -> Not in scope
• An in-scope domain is listed as part of certificate, but is not reachable on the hostname or IP address -> Not in scope
• A DNS "PTR" record points to an in-scope domain, but there is no valid "forward" DNS record -> Not in scope

Known Issues

Known issues that are out-of-scope are added to the domains overview as soon as we can to avoid duplicate submissions.

General

• In case that a reported vulnerability was already known to the company from their own tests, it will be flagged as a duplicate
• 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. We may however decide to offer a bonus at our own discretion.
• 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
• Attacks requiring physical access to a victim's computer/device, man in the middle or compromised user accounts
• Reports that state that software is out of date/vulnerable without a proof-of-concept

Infrastructure

• Open ports without an accompanying proof-of-concept demonstrating vulnerability
• Exposed NTP or SNMP ports/services: These are required for certain services.
• Weak/expired/self-signed SSL configurations and SSL/TLS scan reports (this means output from sites such as SSL Labs)

Web application

• API key disclosure without proven business impact
• 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 or Firebase API keys
• Host header injection without proven business impact

Desktop application

• Loading malicious dynamic libraries

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, by requiring developer mode, by enabling USB debugging or by installing malicious apps.
• API key leakage used for insensitive activities/actions

Financial embargoes and sanctions

We are unable to issue rewards to individuals in regions that are subject to financial embargoes or similar sanctions imposed by national or international authorities such as the European Union and the United Nations. This restriction is in line with our commitment to legal and ethical business practices and is designed to ensure full compliance with applicable laws.

This program follows Intigriti Triage standards

Due to the limited impact on our organization, (sub)domain takeover vulnerabilities will be downgraded by 1 CVSS classification level (typically: High to Medium).

No FAQ at this time.