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 Tremendous to award.

Introduction

We are happy to announce our Vulnerability Disclosure Program (VDP)! We've done our best to clean up our known issues and now would like to request your help to spot the ones we missed!

Our worst-case scenarios are:

There's two scenarios that keep us awake at night:

1. Remote account takeover: being able to takeover one of our customers accounts and drain their balance;
2. Exposing existing rewards: enumerating payouts that have already been sent and redeeming them.

Any useful infrastructure information:

Primary domain & API:

• tremendous.com (marketing site)
• app.tremendous.com (customer dashboard)
• api.tremendous.com (public API)
• reward.tremendous.com (recipient page)

Sandbox environment (mirrors production, but no real money involved):

• app.testflight.tremendous.com (customer dashboard)
• api.testflight.tremendous.com (public API for integration testing)

Authentication & Access Control:

• We use industry-standard authentication and authorization mechanisms.
• Researchers should focus on misconfigurations, privilege escalation, and improper session handling.

Technology Environment (high-level):

• Reverse proxies and WAF (Cloudflare).
• Core services orchestrated on Kubernetes.
• Common web technologies (REST APIs, standard HTTP methods, JSON payloads).

Data Sensitivity:

• Platform handles financial transactions, personal recipient information, and payment instrument distribution.
• Researchers should prioritize vulnerabilities impacting confidentiality, integrity, or availability of this data.

Bounties

This is a responsible disclosure program without bounties.

Marketing video example

https://www.youtube.com/watch?v=pqZ2pVMddcU

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.

Application

• 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 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

Mobile

• 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)
• API key leakage used for insensitive activities/actions

LLMs

• Any prompt injection that does not lead to an actual undesired change in behavior (e.g.: only leaks the system prompt)

This program follows Intigriti's triage standards based on the proof of concept.

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.