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 PoCs on YouTube and Vimeo)

Scope Leniency

This program will not accept submissions for assets that are not listed as explicitly in scope.

Program Rules

• Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
• Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
• When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
• Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
• Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
• Note that the domain support.lightspark.com and the email address support@lightspark.com are out-of-scope. Please do not attempt to use this domain or email address as their use will potentially disqualify you from future rewards.

Introduction

We're happy to announce our program! 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!

Focus Areas:

At Lightspark, we deal with customers' financial data on a day-to-day basis. For this Bug Bounty Program, we'd like you place extra emphasis on the following types of findings:

• Business Logic Errors which may lead to manipulation of transactions, payment flows and fee bypasses and other activity which could lead to financial damage
• Broken Access Control / Insecure Direct Object Reference (IDOR): Unauthorised access to other tenants' actions or account information
• Account takeover attacks
• Findings relating to authentication/authorization mechanisms
• Sensitive data exposure: This will include sensitive information such as account balances, PII and other information

*Please note that for the Spark SSP, showing how an outside party could compromise or impersonate the SSP is in scope, but malicious behavior by the SSP is currently out of scope.

Any useful infrastructure information:

The following links are available to help with Bug Bounty research:

• https://docs.lightspark.com/

Specific to this program

For this particular program, the following items are Out of Scope:

• Attacks against Spark requiring a malicious SO
• Showing how an outside party could compromise or impersonate the SSP is in scope, but malicious behavior by the SSP is currently out of scope.
• Known vulnerable libraries without a working PoC: Reports of vulnerable libraries should include a PoC demonstrating that the library is actually exploitable as used in the relevant application
• Attacks targeting support.lightspark.com and support@lightspark.com: We would like to emphasize that attacks against these two targets are strictly out of scope. Please do not attempt to use this domain or email address as their use will potentially disqualify you from future rewards.

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
• Typically, issues that only allow a user to interfere with their own use
• 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

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.

For testing the product at https://app.lightspark.com:

You can sign up for an account and use the service in Test Mode.
The API endpoint is located at https://api.lightspark.com/. You can find the API documentation at https://app.lightspark.com/docs (an account is needed for access).

For testing the product at https://link.uma.me and link.uma.money:

To sign up for a account, you may use your own information if you choose on https://link.uma.me https://www.uma.money.