For Sol1, next to open source, security is core to our values, and we value the input of hackers acting in good faith to help us maintain a high standard for the security and privacy for our users. This includes encouraging responsible vulnerability research and disclosure. This policy sets out our definition of good faith in the context of finding and reporting vulnerabilities, as well as what you can expect from us in return.
When working with us, according to this policy, you can expect us to:
- Respond to your report promptly, and work with you to understand and validate your report;
- Strive to keep you informed about the progress of a vulnerability as it is processed;
- Work to remediate discovered vulnerabilities in a timely manner, within our operational constraints; and
- Recognise your contribution to improving our security if you are the first to report a unique vulnerability, and your report triggers a code or configuration change.
- Extend Safe Harbour (see below) for your vulnerability research that is related to this policy.
To encourage vulnerability research and to avoid any confusion between legitimate research and malicious attack, we ask that you attempt, in good faith, to:
- Play by the rules. This includes following this policy any other relevant agreements;
- Report any vulnerability you’ve discovered promptly;
- Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience;
- Use only the Official Channels to discuss vulnerability information with us;
- Handle the confidentiality of details of any discovered vulnerabilities according to our Disclosure Policy;
- Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope;
- If a vulnerability provides unintended access to data: Limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept (PoC); and cease testing and submit a report immediately if you encounter any user data during testing, such as Personally Identifiable Information (PII), Personal Healthcare Information (PHI), credit card data, or proprietary information;
- You should only interact with test accounts that you own, or with explicit permission from the account holder; and
- Do not engage in extortion.
All of Sol1’s assets are in scope unless otherwise stated in the Out-of-Scope section below. This includes:
We will only acknowledge submissions that have real-world impact. To better prove this impact, a working Proof of Concept (PoC) is highly recommended and may result in a better outcome. We will not accept theoretical vulnerabilities such as TLS vulnerabilities and missing security headers, unless you can show impact.
The following lists the scope and attacks that are excluded from this policy, meaning that we do not give consent to test against these assets/methods:
- Social engineering of any kind;
- Physical attacks against Sol1, its employees or any property belonging to Sol1 of its employees;
- (Distributed) Denial of Service of any kind;
- DNS/subdomain brute-force enumeration;
- HTTP virtualhost/SNI brute-force enumeration;
- Services attached to CNAME records resolving to out-of-scope domains (for example domains.sol1.net is an alias to www.partnerconsole.net which is out-of-scope);
- Actions that violate Australian law. Although submissions with no impact will be reviewed, they are unlikely to be accepted as part of this program. Some example of submissions that won’t be accepted are:
- Missing HTTP headers that don’t have impact;
- Out-of-date software/libraries unless you can prove their impact;
- Theoretical SSL/TLS findings;
- “Best practice” configurations that do not have impact; and
- “Self” exploits (such as Self-XSS) and exploits that required significant actions from users.
Vulnerabilities discovered or suspected in out-of-scope systems should be reported to the appropriate vendor or applicable authority.
All submissions should be sent to security (at) sol1 (dot) com (dot) au. If you feel you need to encrypt the submission (we are in favour of this), please put your report in a separate file, encrypt that file using the PGP key below and attach it to the email.
Fingerprint: FAFD 2A29 EC39 2E04
-----BEGIN PGP PUBLIC KEY BLOCK----- mQINBGIqx7UBEACitxr4mBV4NT7vpcechrYPWq1uh+xc2Cf4iCCfKW7Dxr8uqngK HZ/6T1bhYEX3CeyfIM+2ad7903M1xb5vzGKIUUi/dqHLoObHJAS2g7PBf0fP6rey 91PC5qqnW9Pj0l2Rk7t3f1hcATuvChkkJ6wDmvyUNywyM5Gkg1xmBPKNmCjnCW6l jipHMtsW3vFO7d/lzuf19pxOORwPKp1v7LP0ic9K3QK+fdP73qcCH5YvxyAhcvhr nTTgOlJNuj80KHUz11p7mm9cPnKZIkMNSMp0j3/5gw9/HnRUlLZPhFEqDHmrOVPI rPdmlUFbRNmShAknT3xdLCWCdgKEcNE4q3aecov1cmgLmgbBRu5RoWL1GAZxL0K7 kbAsxK9jDDp/qMi3QU+/lDlGvr7uI4kTYJxwu7rB8SG4RwqjyuwfYzFDQQayrr7c VB+BbVVf7apaL9Duzqy4jBOx7IvlCXPtYSz6BH7IV8yBa7UDKAbxBExo8e1dhFUo 3F7whilAStl3Qt11Z76X1kmtv5tEl8iRJIkG27zqekWiq/5QgzTYVF8iZKk5RAe+ fWIqxGPnv7vfhEafd6xSTtL+0Vo4Te6u06b46Tv8uWbhS+SZZJVSmNkrT4qe8sRp KfaTiDlwqkbwNHsGnfLLA8ooUYSJRUd+VAcUF3MN6iwcfZ8H5I0si2sdgQARAQAB tERTb2wxIFNlY3VyaXR5IChLZXkgZm9yIHNlY3VyZSB2dWxuIHJlcG9ydGluZykg PHNlY3VyaXR5QHNvbDEuY29tLmF1PokCUwQTAQoAPgIbAwULCQgHAgYVCgkICwIE FgIDAQIeAQIXgBYhBDJil19F6H2zs8MSg/r9KinsOS4EBQJiKsfLBQkDw53rAAoJ EPr9KinsOS4Ek/IP+L+RMnB2W0DxVzBfllm4RBi2BBwmMHvTeVcyPQyg/1/N0ixj /u5SFeOdkDHJFgdL8VIhxpsiLl1jLLAstqa0HOsGfaaj6g4hdMR5M9wz75OANV9R 3zMgk0yy9snwjH6qgyIXWsCIcgQrAd6VRThXFt+khJoVspGpAKVS8Srm15XVz/16 2iS6+ydpgHu8LP1MEU0BMOGbGsBoKKcQvXw/YVIVNBL+7EgfEBE0a3NI6Bp6XAwu KmUz6H1GQ79eNGJG2JE3TYd/BQ7JyXGDfLdyg4VpfVnjrq7FF+mvpNFNrYO92klq cCeXA5HVFayATxQqS8kc5pWPs99o0dkgVyZZcKQch6kxsUrcLJqHlfxF4lcI2rjF ryiluYmba90/EduNQBssNBPsokYecc2cxnH/qsZE05I4yOx18yCjk8tBaUvEb/4e F4n5wOnKONQgGE3OpE4x7nG37kfp8D1B2ocUxLEnGLQSJWtknK/j9HYiDa1E2lU/ jy/DbwfCQ9CLokzfpVN3HU5dMRH0iGBFr40CiafGIShAc+9KrvZjcQ/FVwwq5QuB C42AWfYCag6U54tZv85IVjufhUBPbrCxi/IpQPlnDpfPNHDgAvp84m55KjVq+EhD RGjibdFeFIQHR+ZI5RlpoHUSszNGi2c3jBPW/Xkeh/CLrHgYzSrSR7mL7je5Ag0E YirHtQEQANHlHsmSLyMg+0wmwrOY03TyMeCcZn1z2vgmV3PA0LTJQfM3z5arzO2v 7U+dEGPSB6WopJpOEz4bbRIDRpJomfnLvY3+C3NIWFrikDFfbq7JkHGRKVc2TLQP X1kEiOQljtHh9oWZzh605WLtFlpJIGwpcFXQ8D7bY9+c7uZUDCsGt4Ia4VrwWQYR PCsbfsi5WSuanoq20hbI5zl0Q4S3ge8zsg7bMkmvOrro+sJdRkcPlP7OMxLEQvYM c52A86mZ32lI6UlmklUIBbWXWNTQzh7VzNOeVNsNa9e3Ouvu+G4wqb/CwzX6cUT6 wLI98Gm7T7Pcz9nHX3FhD232gDX9ZlqYNJ4idPB1Afjq5j6xJ+SDWI4z4SSIItYH X8g3SbjkrX7CosXUzU8IbnJNPX2sa4MmfQQmbKxHl+Q4xUnGNqICiLZoYjJ/3kyr pfm1rpVL9ArRBTIV8cF4+XLUal5ldodr1pgkuuu896RrEYYc1/DDSvYVH4hx8d4r vfitwOz8Su77GJhBd33igkbtBzuEFWr1kEusbQdnxnejxEW8e1OdNNLAq16Hxe/v RzO3kg+wAGTz1AR87qIr0erX0ceKrgopZYApjg3o4+OaXoN5fZPkYCyVNlf7SCk1 3VVUwVRzOLWH7w4Xhlh9H1JQAmo7agPSO9NReRQA+tN2spcpPkqDABEBAAGJAjwE GAEKACYCGwwWIQQyYpdfReh9s7PDEoP6/Sop7DkuBAUCYirH5QUJA8Od6wAKCRD6 /Sop7DkuBP5iD/4rZoqoSfzCziUpHx3xWlANP8vIVJy7gbtwvVhNZ/fgyKN2qeOn CtP8POBVt4nlVighYy+KoLyH5o8f2tuqPDTKOdpkpidtxuzBE6E8MRdA4Ixwwr/n poFlztz5W1AR3axmACexGdESLmA6674Z9F+Om5AChWWdVz+bFhIGl3iytO/gK1rm +9imz3HdcyNLqqyPfdZA+UFdJx1iXhB4eT41yp7sbjMHo4cavZIobr1gPTNDIzgk I00hlxRhkjukAhOUFSIVWrFfLREu3pnvvMwiw+CQqQKJwl9JCHsOLvcCSNdz6UKO VE+JL8yYGnn0zMFvVYNinHZx/bGiYwyMjD9cPHDd+MY0yy3/5TiCmB7HPJDaksaj jr98Dx7caJLUWNOzG6f0x8mdZ+HNaZwSEHgM+70Dw3HIqL37EQpvu7roUsxbZJLC anIZTWFPJ42FzX98yTEO9t9iS9xi6Fz6sBmBOKccHFRp6BEtCdgbKNjhvRYnB0LW 4wooADgtUagKCVMwAoXKUYZdVub2vEYqFbFLu9i4Y229haO/nRETWg/n3U6H0X0/ RzgYRxgZ+iCr952h2gl5FV91J/l36pmo/8l3YqbetBzB1iww/pmTc5EbTTIm2yeb 24uEersMCrhXqOQTsa3KZsp9yVsWonKg6bRA27QiqHpUdsRQZEmqts/DnA== =Jw4w -----END PGP PUBLIC KEY BLOCK-----
Discretionary Disclosure: The researcher or Sol1 can request mutual permission to share details of the vulnerability after approval is explicitly received.
We value the work of researchers and the benefit of public disclosure. To that end, we encourage researchers to request permission from us prior to disclosing their findings. If permissions is granted, the researchers should ensure that any sensitive and confidential information is removed or redacted prior to publishing. We would also appreciate receiving a link to any publication.
When conducting vulnerability research according to this policy, we consider this research conducted under this policy to be:
- Authorised in view of any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good faith violations of this policy;
- Authorised in view of relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls;
- Exempt from restrictions in our Terms and Conditions that would interfere with conducting security research, and we waive those restrictions on a limited basis; and
- Lawful, helpful to the overall security of the Internet, and conducted in good faith. You are expected, as always, to comply with all applicable laws (we reside in Australia and thus its laws likely apply, plus laws relevant to the location of the servers you connect to). Note that the Safe Harbour applies only to legal claims under the control of the organisation participating in this policy, and that the policy does not bind independent third parties. If legal action is initiated by a third party against you and you have complied with this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our Official Channels before going any further.
We reward based on the impact of the finding, the quality of the report and how much effort went into the PoC. Please keep in mind that we are a small company.
Rewards are based on the severity of the vulnerabilities, as outlined in Bugcrowd’s Vulnerability Rating Taxonomy:
|Indication of Reward Range||($ are AUD)|
|P1||$512 – $1024|
|P2||$256 – $512|
|P3||$64 – $256|
|P4||$32 – $64|
All accepted submissions receive a mention in our Contributors list below.
The final decision for the reward amount is at our discretion.
Although we can’t reward dupes, we aim to reduce the chance of their occurrence by aiming to fix accepted submissions within 60 days.
We’d like to thank the following people for their awesome contribution to Sol1’s security, the security of our customers and the security of the Internet. You all rock!
- Ashutosh Nath Rimal
- Chirag Ketan Prajapati
- Denis Muhic
- Gaurang Maheta
- Kunal Mishra
- Mayank Mukhi
- Pramod Yadav
- Praveen Mali
- Praveen Yadav
- Rajesh Tewari
- Ronit Bhatt
- Safwat Refaat
- Shivam Pravin Khambe
- Shivani Nimbre
- Vemula Bhavani Shankar
- Vitesh Walunj
- Yash Devkate
Changes to this Policy
This policy is a working document and is subject to change without notice.