Reporting a security issue
CardUp cares deeply about our services, platform and infrastructure security. We encourage researchers and individuals from the security community to report your findings to us, and we are committed to working with you. If you discover a vulnerability, kindly let us know so that we can take the necessary measures to address it as quickly as possible.
How to report a security issue
You can report a suspected security issue by emailing email@example.com. Please include the following details to help us better understand the nature and scope of the issue.
- Date & time when the issue was discovered
- The URL(s) of the affected system
- All relevant headers & parameters used to demonstrate the risk against the CardUp app
- Operating system and browser, with version number, used for all
- Type of issue
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code
- Impact of the issue, including how this could be exploited
- Screenshots of the successful exploitation, if possible
- Your name, email and any other contact details
- Any other information that will help us triage the report more quickly.
What CardUp will do
- provide an initial acknowledgment of your security report.
- follow up with additional questions to ensure we fully understand the report and its potential impact.
- notify you about the progress of our analysis and verification, and any required remediation steps along the way.
- use the Common Vulnerability Scoring System (CVSS) — an industry-standard calculator — to determine the severity of the bug.
- take additional steps internally to remediate once your reported issue has been validated. You will be notified of the subsequent course of action.
- provide you with cash rewards or other financial incentives for the detection and resolution of the validated vulnerability — subjected to the type of reported issue (including but not limited to the impact, ease of exploitation and quality of the report).
We thank you for your time & expertise in improving the security of our company and customers.
Here are other secondary security issues that you may report to us as well:
- Same-site scripting, self-XSS, or clickjacking
- CSRF that has no clear, practical security impact (e.g. Logout CSRF)
- Security best practice concerns (e.g. weak password policy)
- SSL/TLS best practices (e.g. weak cipher suites)
- Missing HTTP Headers (e.g. lack of HSTS)
- Email security best practices (e.g. DKIM, SPF, DMARC)
- Reconnaissance or fingerprinting information that has no practical use for exploitation
- Attacks that require physical access to the target’s device/operating system
- Social engineering attacks that require users to be convinced to be compromised
- Vulnerabilities related to deprecated and/or unsupported versions of software
- Third-party integrations that default to fail-open/fail-safe behaviors
- Static/dynamic code analysis results without verification provided of an actual risk