Our promise to you

• We are happy to respond to any questions, please use the button in the right top corner for this.
• We respect the safe harbour clause that you can find below.

Your promise to us

• Provide detailed but to-the point reproduction steps.
• Include a clear attack scenario. How will this affect us exactly?
• Remember: quality over quantity!
• Please do not discuss or post vulnerabilities without our consent (including PoC's on YouTube and Vimeo)
• Please do not use automatic scanners - be creative and do it yourself! We cannot accept any submissions found by using automatic scanners. Scanners also won't improve your skills, and can cause a high server load (we'd like to put our time in thanking researchers rather than blocking their IP's 😉)

We are happy to announce our first bug bounty program! We've done our best to clean most of our known issues and now would like to request your help to spot the ones we missed. We are specifically looking for

• Call records of (other) customers
• Call recording files of (other) customers
• Horizontal / vertical privilege escalation
• SQLi

See FAQs for test credentials

Shared code disclaimer

In our web application, the description widget in the forms shares the same codebase. Only one submission will be considered as valid when the same vulnerability is reported on all of these different forms.

Our pages with on hover tooltips use the same package/code for displaying them, we will only select one submission related to all tooltips.

VoIP

• Everything related to VoIP (calling)

Application

• Php info information disclosure
• 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 the case that a reported vulnerability was already known to the company from their own tests, the report 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 receives 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

All our rewards are impact based, therefore we kindly ask you to carefully evaluate a vulnerability's impact when picking a severity rating. To give you an idea of what kind of bugs belong in a certain severity rating we've put some examples below. Note that depending on the impact, a bug can sometimes be given a higher/lower severity rating.

Exceptional

• RCE (Remote Code Execution)

Critical

• Access to (other) customer call records
• Access to (other) customer call recording files
• SQL injection

High

• Privilege escalation
• Authentication bypass on critical infrastructure

Medium

• XSS
• CSRF with a significant impact

Low

• XSS that requires lots of user interaction ( > 3 steps)
• Open redirect

Where can we get credentials for the app?

You can use the get credentials button in the right top corner to request credentials that are ready to use! Feel free to reach out to support if you have any issue with these credentials.

On the first Monday of every month, the environment will be wiped and repopulated. However the credentials will always stay the same.

What account types do you have?

Our platform works with 2 different types of users / entities: Partners and Clients. A client can be seen as a tenant for a single company. A partner is a tenant that holds/sells to many clients. Our platform can have multiple partner tenants containing multiple client tenants.

When do you have privilege escalation?

Not only limited to but an extra example for our platform

• When a partner can see other partners or clients that don't belong to their own partner.
• When a client can see other clients or partners in general.

How do I receive (password reset) emails?

Since our current environment is populated with fake data, we only allow emails to be sent to your @intigriti.me email address. If you want to receive emails, make sure you change your test credential user email to your @intigriti.me address.

How do I view call records?

In the call overview, you need to ensure you are filtering on the right time period. Since we generate new data the first Monday of every month, only data will exist for the previous month.

How do I test VoIP calling?

Currently all features related to VoIP calling are disabled and out of scope. This will be enabled in the near future.