Cloudsmith aims to keep its Service safe for everyone, and data security is of utmost priority. If you are a security researcher and have discovered a security vulnerability in the Service, we appreciate your help in disclosing it to us privately and giving us an opportunity to fix it before publishing technical details.
Cloudsmith will engage with security researchers when vulnerabilities are reported to us as described here. We will validate, respond, and fix vulnerabilities in support of our commitment to security and privacy. We won’t take legal action against, suspend, or terminate access to the Service of those who discover and report security vulnerabilities responsibly. Cloudsmith reserves all of its legal rights in the event of any noncompliance.
If you identify a verified security vulnerability in compliance with this Security Disclosure Policy, Cloudsmith commits to:
- Acknowledge receipt of your vulnerability report in a timely manner;
- Notify you when the vulnerability is fixed; and
- Publicly thank you for your responsible disclosure and for helping us stay safe.
Please note that in absolutely no event are you permitted to access, download or modify data residing in any other Account, or one that is not registered to you; unless permission is expressly provided by the Account Owner.
We are pleased to offer thanks and/or a bounty reward for vulnerability information that helps us protect our customers as thanks to the security researchers who choose to participate in our bug bounty program. This will range from the public thanks to a small monetary amount or loot of some sort (depending on our budget). Cloudsmith will decide the bounty reward at our sole discretion, and all decisions are final.
- Upon acknowledgment of a viable exploit we will discuss the options with the reporter.
- We will add the reporter's name/link to the Hall of Fame alongside exploit details.
- If a bounty was determined this will be issued on resolution exploit resolution.
If a monetary award is provided as a bounty then you are responsible for paying any taxes associated with the reward. We are obliged by law to report any such awards to the tax authorities, so please ensure that you handle this appropriately.
The vulnerability classifications that are considered in-scope are:
- Access Control Bypass;
- API Misuse Issues;
- Authentication (Broken or Bypassed);
- Business Logic Issues;
- Cross-Site Scripting (XSS);
- Cross-Site Request Forgery (CSRF);
- Complexity Bomb;
- Decompression Bomb;
- Directory Traversal;
- Improper TLS protection;
- Open URL Redirection;
- Privilege Escalation;
- Provisioning Errors;
- Remote Code Execution (RCE);
- Sensitive/Private Data Leaks;
- Session Fixation;
- Session Management (Broken or Bypassed);
- Subdomain/Domain Takeover;
- SQL Injection.
If a vulnerability isn't explicitly listed here as either in-scope and isn't explicitly mentioned in the next section as out-of-scope then it might be applicable, but we reserve the right to determine this in communication with the security researcher.
The following actions/areas are not considered to be in-scope:
- Executing or attempting to execute any Denial of Service (DoS) attack; or
- Knowingly posting, transmitting, uploading, linking to, sending or storing any Malicious Software; or
- Attempting to social engineer support staff; or
- Testing in a manner that would result in the sending of unsolicited or unauthorized junk mail, spam, pyramid schemes or other forms of duplicative or unsolicited messages; or
- Testing in a manner that would degrade the operation of the Service; or
- Testing or otherwise accessing or using the Service from any jurisdiction that is a Prohibited Jurisdiction; or
- Testing third-party applications or websites or services that integrate with or link to the Service.
The following URLs are also out-of-scope because they're being moved/deleted:
- https://cloudsmith.io/ (root page)
Websites/services that are explicitly NOT considered to be in-scope:
- [Corporate Website (https://cloudsmith.com) - this is temporary until we fully launch it, and then it will be considered as in-scope.
- Help Website (https://help.cloudsmith.io) - this is hosted by https://readme.io.
- Blog Website (https://blog.cloudsmith.io) - this is hosted by https://ghost.io.
- Status Website (https://status.cloudsmith.io) - this is hosted by https://statuspage.io.
- Changelog Website (https://changelog.cloudsmith.io) - this is hosted by https://getbeamer.com.
- Amazon Web Services (https://aws.amazon.com/) - this is our infrastructure provider.
- Any thirdparty widgets, such as:
- Any websites under the following domains:
- *.readme.io (incl. dash.readme.io and cloudsmith.readme.io)
In order to start the reporting process, please share the details of any suspected vulnerabilities with the Cloudsmith Security Team by sending us the details to [email protected]. Please do not publicly disclose these details outside of this process without explicit permission.
In reporting any suspected vulnerabilities, please include the following information:
- Vulnerable URL: The URL where the vulnerability occurs;
- Vulnerable Parameter: If applicable, the parameter where the vulnerability occurs;
- Vulnerability Type: The type of vulnerability;
- Steps to Reproduce: Step-by-step information on how to reproduce the issue;
- Screenshots: A demonstration of the attack to aid description; and
- Attack Scenario: An example attack scenario may help demonstrate the risk and get your issue resolved faster.
Cloudsmith reserves all rights for deciding on scope, impact and reward. If another researcher has previously reported an exploit, only the first disclosure will be considered. However, you'll always have our appreciation, and we'll let you know if this is the case.
Thank you for helping us to make the world of package management that bit safer.
Updated 5 months ago