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 😉)

IMPORTANT: Please only perform service degradation attacks or horizontal privilege attacks on the Sandbox URL's

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;

• Leaking of large quantities of personal data, if you can find a way to expose bulk quantities of data, we want to know about it.

• Horizontal privilege escalation i.e breaking into someone elses wallet. This should only be attempted in the Sandbox environment.

  • This includes being able to see another users details; transactions, balances and the like.

• Specifically related to our trading business, we want to know if you're able to "create money", duplicate transactions or receive more funds into your wallet than are transferred. Any kind of issue which would negatively affect the balance sheet.

• For the "Uphold Card" functionality, being able to see the 16 digit card number or PIN for another user is a big one.

• Third party services are out of scope unless the issue is caused due to a misconfiguration by Uphold

Application

• 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
• Creating apps in Sandbox is allowed (so if you find you can in Production, it's an issue, but not in Sandbox)

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

AWS Specific

• Publically readable S3 buckets. We have a selection of our S3 buckets available to the Internet as caches for our website and other public resources - UNLESS it is clear that the information should not be public, i.e. personal data, company confidential files and such. Please log a ticket if you're not sure with examples of the folder structure (do not download the data)

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
• Self-XSS that cannot be used to exploit other users
• Lack of jailbreak & root detection
• Crashes due to malformed URL Schemes
• Lack of binary protection (anti-debugging) controls, mobile SSL pinning
• Snapshot/Pasteboard leakage
• Exploits only possible in a jailbroken environment
• API key leakage used for insensitive activities/actions
• Attacks requiring physical access to the victim's device
• Attacks requiring installing malicious applications onto the victim's device
• Attacks using OS vulnerabilities, for instance an attack using a vulnerability on a specific android / iOS version

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.

How can I test with funds?

On the Sandbox, it's connected to crypto TestNets, so you can print as much money as you need, to test the platform!