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

• ONLY USE YOUR INTIGRITI.ME ADDRESS (in case of violation, no bounty can be awarded)
• 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 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 once we missed! We are specifically looking for

• leaking of personal data
• horizontal / vertical privilege escalation
• ...

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

• A remote code execution vulnerability on the production server
• Full database access (incl. update/delete)

Critical

• A SQL injection vulnerability
• Access to all customer personal data or access to a targeted user
• A numeric IDOR that allows mass write/read actions on critical features
• Path traversal leading to the disclosure of local files

High

• Access to random users' data (sensitive PII)
• A stored XSS vulnerability (excluding unexploitable self-XSS)
• Vertical authentication bypass

Medium

• A DOM XSS vulnerability
• Reflected XSS
• An IDOR leading to the disclosure of non-critical data
• A CSRF with a significant impact
• Lateral authentication bypass

Low

• A reflected XSS vulnerability that requires significant user interaction
• A CSRF vulnerability in a non-critical feature
• Open redirect

Cool-down period for zero-days

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!

Where can we get credentials for the app?

We currently don’t offer any credentials to test user roles.