Guidelines

• Provide detailed but to-the point reproduction steps
• Include a clear attack scenario, a step by step guide in the PoC is highly appreciated
• Remember: quality over quantity!

We're interested to hear about any issue that potentially compromises our company or its user's security. Before submitting a vulnerability, make sure to check that it's not listed in our out of scope policy (which you can find below). If you have additional questions about our program feel free to contact us through intigriti's support by using the button on the right hand side (Ask scope question).

No reward for out of scope bugs

• You will not receive a reward and your submission might be rejected if they are out of scope.
• Out of scope are domains/IPs/.. not listed in the in-scope section. If in doubt don't hesitate to reach out to us via the support button in the top right corner.
• Brute Force / Automated Scans
• Third party services, except for misconfiguration issues

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

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 Delen Private Bank on the criticality of the impact and only if the submission was the first of its kind and agreed to be valid.

Exceptional

• Access to sensitive client data
• Full database access

Critical

• Remote Code Execution
• Access to sensitive user/employee data
• SQLi
• Full privileged access to an important asset of the infrastructure
• Ability to make transactions/orders

High

• Stored XSS
• Access to random customer's data

Medium

Vulnerabilities that affect multiple users, and require little or no user interaction to trigger:

• XSS (single click)

Low

• Debug stack trace
• XSS with complicated scenario's
• Open redirects with possible security impact

Test accounts

Test accounts are not given at this moment. All testing should assume black-box testing. Of course if you find credentials on other places that might give you more access to our systems, we'd love to hear about it!