At Splitwise, we’re lucky to have supportive users who help us to find bugs and potential security vulnerabilities via responsible disclosure. If you believe you have discovered a potential issue with our system, we appreciate your help in disclosing the issue to us responsibly. This page contains info on how to report an issue, and gives thanks to all the individuals who have reported issues in the past.
Researchers who submit a valid report to us within the bounds of this policy will be given credit and thanks on this page once the submission has been accepted, remedied, and validated by our security team.
How we approach security reports
- Splitwise will not take legal action against users for disclosing vulnerabilities as instructed here.
- Valid vulnerability reports will always be responded to as fast as possible – usually within 2 business days.
- If we agree that you’ve reported a valid issue with our service, we’ll attribute you with a special thanks on this page after the issue has been remedied. Please let us know if you’d like us to include a link to your Twitter account or other profile.
Guidelines
To promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:
- Share the security issue with us in detail right away by emailing us at security@splitwise.com.
- Don’t perform any actions that could harm the reliability or integrity of our services and data. Some examples of harmful activities that are not permitted include: brute forcing, denial of service (DoS), spamming, timing attacks, etc.
- Don’t use scanners or automated tools to find vulnerabilities.
- Do not engage in social engineering or phishing of Splitwise users or employees.
- Please give us a reasonable time to respond to the issue before making any information about it public.
- Do not access or modify our data or our users’ data. Only interact with your own accounts or test accounts for security research purposes.
- Do not view, alter, save, store, transfer, or otherwise access to any data obtained incidentally during your research, and immediately purge any local information after reporting the vulnerability to Splitwise.
- Act in good faith to avoid privacy violations, destruction of data, and interruption or degradation of our services (including denial of service).
- Comply with all applicable laws.
In the event of duplicate reports for the same issue, Splitwise will generally only add the first person to report the issue to our Responsible Disclosure page.
We reserve the right to disqualify individuals from the program for disrespectful or disruptive behavior. We will not negotiate in response to duress or threats (e.g., we do not offer cash rewards and will not negotiate a payout amount under threat of withholding the vulnerability or threat of releasing the vulnerability or any exposed data to the public).
Third-party services
Some subdomains of splitwise.com are run via third-party services. If you find an issue with one of these subdomains, you may want to report it directly to the appropriate company, depending on the issue:
- feedback.splitwise.com runs on UserVoice
- dev.splitwise.com runs on GitHub Pages
- blog.splitwise.com runs on WordPress.com
Out-of-scope issues
The following issues are generally considered out-of-scope and not eligible for thanks. We try to respond to every report within 48 hours, but we may be slower to respond to reports about the following:
- Our policies on presence/absence of SPF/DMARC records.
- Password, email and account policies, such as email id verification, reset link expiration, password complexity.
- Host header injections, unless you can show how they can lead to stealing user data.
- Attacks requiring physical access to a user’s device.
- Reports of spam (i.e., any report involving ability to send emails without rate limits).
- Missing best practices (we require a repeatable proof of concept demonstrating a security vulnerability).
- Any physical attacks against Splitwise property, offices, or employees.
- We will only accept critical reports in blog.splitwise.com (e.g., RCE). Minor issues that can’t impact Splitwise users are out of scope. Please report them to the Automattic Program.
- Clickjacking on domains other than www.splitwise.com or secure.splitwise.com.
Special thanks to all those who have helped Splitwise:
2022
2021
2020
- Pritam Mukherjee
- Gourab Sadhukhan
- Rajat Sharma
- Bindiya Sardhara
- Syed Mushfik Hasan Tahsin
- Cheryl Maise Lobo
- Aman Sinha
- Vasu Yadav
- Nicolas Briand
- Agnieszka Pietruczuk
- Kshitiz Raj
- M Tayyab Iqbal (Alpha Inferno Smc Pvt Ltd)
2019
- Bugra Eskici
- Kyle Cooper
- Hunter Abubakar
- Abid Gul Shahid
- Jens Müller
- Arshad Aqil K
- Jagadeesh V
- Tung Pun
2018
- Lazim Mohammed
- Anshuman Joshi
- Shivankar Madaan
- Johne Jacob
- Ismail Tasdelen
- Vineet Kumar
- Suhas Sunil Gaikwad
2017
- Amal Jacob
- Yan Pritzker
- pavanw3b
- Mico Infante
- Amal Jacob
- Kartik Singh
- Deepthi Kandasubramanian
- Johne Jacob
- Jolan Saluria
- Robin “Japz” Divino
- Johne Jacob
- Pethuraj M
- Guifre Ruiz
- James Reggio
2016
- Muhammad Osama
- Mansoor Gilal
- Bilal Javed from Cyphlon
- Alec Blance
- Konduru Jashwanth
- Ranjan
- Graziano Misuraca
- Ye Yint Min Thu Htut
- Yogeesh Seralathan
- Chaitanya Kanuri
- Eusebiu Blindu
- Mahmoud Osama
2015
- Wiswat Aswamenakul
- Hammad Qureshi & Huzaifa Jawaid
- Balaji P R
- Raghav Bisht
- Ashesh Kumar
- Yatin Sirpaul
- Shvm Gpta
- Ashutosh Kumar
- Omer Iqbal
- Prashant Padmashali
- Kiran Karnad
- Eds Keizer
- Sarah Harvey from Square
2014
- Alec Ferguson
- Rakesh Singh, Harish Kumar and Sandeep Sodhi
- Simone Memoli
- Yash Pandya
- Sherin Panikar, Praveen Nair, Indrajith AN (KeralaCyberSquad-India)
- Muhammad Talha Khan
- Meris Bihorac
- Soufiane Ouha
- Nakul Mohan
- Hardik Tailor
- Shahmeer Amir (Maads Security)
- Narendra Bhati
- Mohamed M. Fouad
- Shubham Gupta
- Tanuj Jane
- Scott Glossop and Oliver Bayes-Shelton
- Evan Ricafort
- Thalaivar Subu
- Roshan Bharathi
- S.Venkatesh
- Kiran Karnad
- Abdul Wasay
- Abdul Haq Khokhar
- Abdul Rehman
- Priyesh Patel
- Mohamed Abdelbaset Elnoby
2013
- Sandeep Kamble
- Sahil Saif
- Kamil Sevi
- Shashank Kumar
- Saurabh Chandrakant Nemade
- Daksh Patel
- Vikas Chopalli
- Denis Kolegov
- Tejash Patel
- Shubham Raj
- Vishnu Patel
- Ehraz Ahmed
- Umraz Ahmed
- Sunil Dadhich
- Vaibhav Deshmukh
- Sebastian Neef
- Narendra Bhati
- Ketankumar B. Godhani
- Arvind Singh Shekhawat
- Nitesh Shilpkar
- Ch. Muhammad Osama
- Ishan Anand
- Pankaj Singh
- Vishal V. Sonar
- Vinod Tiwari
- Varun Nair
- Yuji Kosuga
- Jacob Soo Lead Re
- Satheesh Raj