Authorization

This section reflects our commitment to not take legal action against anyone in the general public for security research activities that represent a good faith effort to follow the policy.

If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized. We will work with you to understand and resolve the issue quickly, and TinkerHost will not recommend or pursue legal action related to your research. Should legal action be initiated by a third party against you for activities that were conducted in accordance with this policy, we will make this authorization known.

Guidelines

Once you’ve established that a vulnerability exists or encountered any sensitive data (including personally identifiable information, or account information), you must stop your test, notify us immediately, and not disclose this data to anyone else.

Under this policy, “research” means activities in which you:

• Notify us as soon as possible after you discover a real or potential security issue.
• 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’s presence. Do not use an exploit to compromise or exfiltrate data, establish persistent command line or use the exploit to pivot to other systems.
• Provide us a reasonable amount of time (about 1-2 weeks) to resolve the issue before you disclose it publicly.
• Refrain from submitting a high volume of low-quality reports, or a high volume of related reports that could be condensed (Quality over Quantity).
• Refrain from the use of automatic scanners. All testing must be confirmed by a living human.

The following test methods are not authorized for your use:

• Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data.
• Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other form of non-technical vulnerability testing.

Scope

The following URIs are in-scope, and should be reported to TinkerHost should a vulnerability be found.

• Everything under the tinkerhost.net domain (tinkerhost.net), including all subdomains and subdirectories, with the exception(s) listed below.
  1. support.tinkerhost.net/forum is independently developed by a third-party. While the infrastructure is within scope, the application(s) themselves are not.

The following URIs are not in-scope, and vulnerabilities should be reported to our provider, iFastNet.

• filemanager.ai
• Scriptinstall.rocks
• Any subdomain including “cpanel” or “sql”, and with a root domain belonging to TinkerHost or iFastNet
• ftpupload.net

Any service not expressly listed above, such as any connected services, are excluded from scope and are not authorized for testing. Additionally, vulnerabilities found in 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 is in scope or not, contact us at security@tinkerhost.net before starting your research.

Out of scope vulnerabilities

The following vulnerabilities will not be considered if submitted. Do not consider this list complete, it can change at any time, and at our own discretion.

• There are no out-of-scope vulnerabilities listed at this time.

Reporting a vulnerability

Information submitted under this policy will be used for defensive purposes only: to mitigate or remediate vulnerabilities. We will not share your name or any contact information without prior express permission.

We accept vulnerability reports via security@tinkerhost.net. Reports may be submitted anonymously. Reports may not be submitted to any other location. We do not support PGP-encrypted emails.

By submitting a vulnerability, you acknowledge that you have no expectation of payment and that you expressly waive any future pay claims against TinkerHost related to your submission. While you may be rewarded for successfully identifying and reporting a vulnerability, do not expect to receive compensation for submitting a report.

In order to help us triage and prioritize submissions, we recommend that your reports:

• Describe the location the vulnerability was discovered and the potential impact of exploitation.
• Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).
• Provide suggestions (If possible) to migrate or patch the security threat.
• Be written in English, if possible.

When you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible. To the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution. You are welcome to ask follow-up questions about the process.