Vulnerability Disclosure Policy

Guidelines

We require that all researchers

• Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security testing.
• Perform research only within the scope set out below.
• Use the identified communication channels to report vulnerability information to us.
• Keep information about any vulnerabilities you’ve discovered confidential between yourself and Debricked until we’ve had 90 days to resolve the issue.
• When you create an account on our service, please use “pentester” as the company name.

If you follow these guidelines when reporting an issue to us, we commit to:

• Not pursue or support any legal action related to your research.
• Work with you to understand and resolve the issue quickly.
• Recognize your contribution on our Security Researcher Hall of Fame, if you are the first to report the issue and we make a code or configuration change based on the issue.

Scope

• debricked.com

Non-bounty Issues

We receive many reports on issues that we do not consider to be a risk for us or our customers. Many of which are included in the list here Please read the list carefully before submitting reports to us.

Out of Scope

In the interest of the safety of our users, staff, the Internet at large and you as a security researcher, the following test types are excluded from scope:

• Findings from physical testing such as office access (e.g. open doors, tailgating)
• Findings derived primarily from social engineering (e.g. phishing, vishing)
• Findings from applications or systems not listed in the ‘Scope’ section
• UI and UX bugs and spelling mistakes
• Network level Denial of Service (DoS/DDoS) vulnerabilities

Things we do not want to receive:

• Personally identifiable information (PII)
• Credit card holder data

How to report a security vulnerability?

If you believe you’ve found a security vulnerability in one of our products or platforms please send it to us by emailing security@debricked.com. Please include the following details with your report

• Description of the location and potential impact of the vulnerability. Here, we regard a vulnerability to be a weakness that can be exploited to violate a security policy in terms of confidentiality, integrity and/or availability.
• A detailed description of the steps required to reproduce the vulnerability (PoC scripts, screenshots, and compressed screen captures are all helpful to us).
• Your name/handle and a link for recognition in our Hall of Fame.
• Currently we are not able to offer monetary rewards. Please be aware of this when submitting your findings.

Note that even though we are happy to receive information about not following best-practices, such issues are not vulnerabilities, unless they affect confidentiality, integrity and/or availability.

Some best practices and issues of low relevance are already in our backlog. They will be fixed but are not prioritized. For this reason, many reports are duplicates of things that have been reported before. However, all customers can rest assured that all important security issues are immediately responded to and fixed.

Here is an excerpts of issues that we deem not prioritized:

• Information disclosure in a Wordpress plugin that refers to publicly available information, affecting the following URLs:
  • https://debricked.com/blog/wp-json
  • https://debricked.com/blog/wp-json/wp/v2/users
• Questionable categorizations done by our proactive password checker
• Do not require 2FA when disabling 2FA (only affecting logged in users)
• No termination of session when adding 2FA

Please respect our decisions and assessments. We are not going to engage in long discussions and arguments regarding best practices and their relevance.

If you’d like to encrypt the information, please use our PGP key.