mobbin.com

Contact: mailto:security@mobbin.com
Acknowledgments: https://mobbin.com/security/hall-of-fame.txt
Preferred-Languages: en
Canonical: https://mobbin.com/.well-known/security.txt

# Vulnerability Disclosure Program

At Mobbin, we consider the security of our systems a top priority. But no matter how much effort we put into system security, there can still be vulnerabilities present.

If you discover a vulnerability, we would like to know about it so we can take steps to address it as quickly as possible. We would like to ask you to help us better protect our clients and our systems.

## Out of scope vulnerabilities

- Clickjacking on pages with no sensitive actions.
- Unauthenticated/logout/login CSRF.
- Attacks requiring MITM or physical access to a user's device.
- Any activity that could lead to the disruption of our service (DoS).
- Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS.
- Email spoofing.
- Missing DNSSEC, CAA, CSP headers.
- Lack of Secure or HTTP only flag on non-sensitive cookies.
- Deadlinks.

## Please do the following

- E-mail your findings to security@mobbin.com in the following format
  - Subject: [CVSS Score]: [Vulnerability] 
  - Body:
    - CVSS Scoring
    - Vulnerability Description
    - Reproduction Steps
- Do not run automated scanners on our infrastructure or dashboard. If you wish to do this, contact us and we will set up a sandbox for you.
- Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying other people's data.
- Do not reveal the problem to others until it has been resolved.
- Do not use attacks on physical security, social engineering, distributed denial of service, spam or applications of third parties.
- Do provide sufficient information to reproduce the problem, so we will be able to resolve it as quickly as possible. Usually, the IP address or the URL of the affected system and a description of the vulnerability will be sufficient, but complex vulnerabilities may require further explanation.

## Disclosure guidelines

- In order to protect our customers, do not reveal the problem to others until we have researched, addressed and informed our affected customers.
- If you want to publicly share your research about Mobbin at a conference, in a blog or any other public forum, you should share a draft with us for review and approval at least 90 days prior to the publication date. Please note that the following should not be included:
  - Data regarding any Mobbin customer projects
  - Mobbin customers' data
  - information about Mobbin employees, contractors or partners
- We may take some time to get back to you. Please be patient with us.
- Mobbin reserves the right to update the terms of this program without notice.

## What we promise

- We will respond to your report as soon as we can.
- If you have followed the instructions above, we will not take any legal action against you in regard to the report.
- If your disclosure is sufficiently significant and if you have been cordial throughout the exchange, you will be given a reward payout if the disclosure was not previously known. Making demands or being rude may disqualify you from your reward.
- We will handle your report with strict confidentiality, and not pass on your personal details to third parties without your permission.
- We will keep you informed of the progress towards resolving the problem.
- In the public information concerning the problem reported, we will give your name as the discoverer of the problem (unless you desire otherwise).

We strive to resolve all problems as quickly as possible, and we would like to play an active role in the ultimate publication on the problem after it is resolved.

This file is shown exactly as published by the domain, as collected by the securitytxthistory crawler. 3,863 bytes · 57 lines.