Vulnerability disclosure policy

As a company trusted by thousands of small businesses, Dubsado has a responsibility to protect all data stored on the platform from unwarranted disclosure. We want security researchers to feel comfortable reporting vulnerabilities they’ve discovered, as set out in this policy, so that we can fix them and keep our information safe.

This policy describes what systems and types of research are covered under this policy, how to send us vulnerability reports, and how to operate with Dubsado in a safe and professional manner.

Guidelines

We require that you:

  • Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.

  • Only use exploits to the extent necessary to confirm a vulnerability. Do not use an exploit to compromise or exfiltrate data, establish command line access and/or persistence, or use the exploit to “pivot” to other systems. Once you’ve established that a vulnerability exists, or encountered any of the sensitive data outlined below, you must stop your test and notify us immediately.

  • Keep confidential any information about discovered vulnerabilities.

Scope

This policy applies to dubsado.com and the following subdomains:

Any services not expressly listed above, such as any connected services, are excluded from scope and are not authorized for testing.

The following test types are explicitly not authorized:

  • Network denial of service (DoS or DDoS) tests

  • Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing

If you encounter any of the below on our systems while testing within the scope of this policy, stop your test and notify us immediately:

  • Personally identifiable information

  • Financial information (e.g. credit card or bank account numbers)

  • Proprietary information or trade secrets of companies of any party

Authorization

If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized, will work with you to understand and catalog your reported issue, and Dubsado will not initiate or recommend legal action related to your research.

We may share your vulnerability reports with affected vendors.

Code of Conduct

There are many considerations when it comes to investigating a bug circumstance. We reply to all requests and categorize them against previously submitted requests. You may not hear back via email upon submitting your research but it doesn't not mean that it has not been processed or considered.

Sending harassing emails or threatening notes should be avoided in order to maintain an amicable flow between Dubsado and the security research community as a whole.

Disclosure

Dubsado is committed to patching vulnerabilities within an appropriate amount of time given the potential impact of the report.

At the same time, we believe that disclosure in absence of a readily available patch tends to increase risk rather than reduce it, and so we ask that you refrain from sharing your report with others.

We will never publish information about you or our communications with you without your permission, likewise, please ask for permission when sharing any pertinent information regarding a report.

Additionally, vulnerabilities found in non-Dubsado systems from our vendors fall outside of this policy’s scope and should be reported directly to the vendor according to their disclosure policy (if any). If you aren’t sure whether a system or endpoint is in scope or not, contact us via ‍before starting your research.

Rewards

Dubsado does not have a Bug Bounty Program.

Reporting a vulnerability

Reports should include:

  • Description of the location and potential impact of the vulnerability.

  • A detailed description of the steps required to reproduce the vulnerability.

  • Proof of concept (POC) scripts, screenshots, and screen captures are all helpful. Please use extreme care to properly label and protect any exploit code.

  • Any technical information and related materials we would need to reproduce the issue. Please keep your vulnerability reports current by sending us any new information as it becomes available.

We accept vulnerability reports via this contact form. Reports may be submitted anonymously, though contact information helps resolve issues and is required to claim bounties.

‍