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)

At the end of every two months (starting from the end of June), we would like to invite the top two researchers from this Program to our Private Bug Bounty Program. All you need to be elegible, is achieve a minimum of 25 reputation points on this Program.

We will validate all submissions within the below timelines (once your submission has been verified by Intigriti):

Critical: 5 working day
High: 5 working days
Medium: 10 working days
Low 10 working days

Working hours = Mo-Fr 9:30am - 6pm (EET)

Domains

• Any domain that is not listed in the Domains section, is out of scope for this program

Application

• 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
• Missing HttpOnly or Secure flags on cookies
• Missing security headers
• Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
• Presence of autocomplete attribute on web forms
• Bypassing rate-limits or the non-existence of rate-limits
• Best practices violations (password complexity, expiration, re-use, etc.)
• Clickjacking on pages with no sensitive actions
• CSV Injection
• Mixed content type issues
• Cross-domain referer leakage
• Anything related to email spoofing, SPF, DMARC or DKIM
• Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
• E-mail bombing
• HTTP Request smuggling without any proven impact
• Homograph attacks
• XMLRPC enabled
• Banner grabbing / Version disclosure
• Open ports without an accompanying proof-of-concept demonstrating vulnerability
• Weak SSL configurations and SSL/TLS scan reports
• Not stripping metadata of images
• Disclosing API keys without proven impact
• Same-site scripting
• Subdomain takeover without taken over the subdomain
• Arbitrary file upload without proof of the existence of the uploaded file
• Comma Separated Values (CSV) injection without demonstrating a vulnerability.
• Any activity that could lead to the disruption of our service (DoS).
• Missing email validation

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, may be excluded or be lowered in severity
• Spam, social engineering and physical intrusion
• DoS/DDoS attacks or brute force attacks
• Vulnerabilities that are limited to non-current browsers (older than 3 versions) will not be accepted
• 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

This program follows Intigriti's contextual CVSS standard

Where can we get credentials for the app?

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