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.

Introduction

We are happy to announce our Vulnerability Disclosure Program! This program should be used for anonymously reporting issues to us. Please note that unlike our bug bounty program, the VDP does not offer financial rewards.

Our worst-case scenarios are:

• Cross-account access to customer data
• Unintended disclosure of personal or sensitve data
• Critical issues like RCE or SQL injections
• Access to internal systems

See our extensive docs for help using our APIs. We advise you to use the sandbox environment for testing so that you do not need to go through our Know Your Customer (KYC) checks. All our payments APIs require KYC, which you will most likely not pass unless you are a genuine customer. Our sandbox environment is very similar to production.

All domains with -sandbox in are for the sandbox environment, and most have a production equivalent without -sandbox. e.g. api.truelayer-sandbox.com is the sandbox version of api.truelayer.com, and has the exact same endpoints.

You may wish to use our Postman and Insomnia collections, and Insomnia signing plugin for performing API requests:

• Quickstart guide for making a payment - Our most up to date/easy to follow documentation
• Data API Postman guide
• Payments V1 API Postman guide
• Verification Postman guide
• PayDirect Insomnia guide
• Payments V3 API Insomnia guide

Zimpler

Zimpler assets are also in scope in the VDP, see docs here.

The contact form at https://truelayer.com/contact/ goes to a third party and SHOULD NOT be tested. Please avoid spamming any contact forms in general, including the live chat. Real people have to review these messages.

Domains

Some of our subdomains point to third-party services and as such MUST NOT be tested. To check if a subdomain points to a third-party you can do a DNS lookup and see if the subdomain is a CNAME pointing to another domain that is not listed in scope. You can also check if an HTTP GET request results in a 302 redirect to a third-party. The only exception to this out-of-scope rule is insecure configurations that TrueLayer is in control of. Please let us know if we have an insecure configuration, but please ensure you abide by any terms and conditions imposed by the third party during any testing. This normally means automated scanners should not be used.

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

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

Where can we get credentials for the app?

For TrueLayer assets, you can self-register in the TrueLayer Console (console.truelayer.com) but please don’t forget to use your @intigriti.me address.

For Zimpler assets, no credentials are available at this time.