The security of our systems is very important to snapWONDERS. While we make every effort to keep our systems secure, vulnerabilities may still exist.

A security vulnerability is a flaw or weakness in the design, implementation, operation or management or a product or service that could be exploited to compromise the confidentiality, integrity, or availability of data.

We are keen to engage with the security community. If you think you have identified a vulnerability in one of our systems, services, or products, please report it to us as quickly as possible.

This policy is intended to give security researchers clear guidelines for conducting vulnerability discovery activities and to convey our preferences in how to submit discovered vulnerabilities to us.

Please note that snapWONDERS does not operate a bug bounty program. By submitting a vulnerability, you acknowledge that you have no expectation of payment and that you expressly waive any future pay claims against snapWONDERS related to your submission. However, we can credit you as the person who discovered the vulnerability, unless you tell us not to.

This policy describes what systems and types of research are covered under this policy, how to send us vulnerability reports, and how long we ask security researchers to wait before publicly disclosing vulnerabilities.

We encourage good-willed security researchers and professionals to report our vulnerabilities to us.

If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorised, we will work with you to understand and resolve the issue quickly, and snapWONDERS 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 authorisation known.

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 access, or use the exploit to pivot to other systems.
• Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.
• Do not submit a high volume of low-quality reports.

Once you’ve established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party), you must stop your test, notify us immediately, and not disclose this data to anyone else.

Our vulnerability disclosure policy does not cover:

• Clickjacking.
• Social engineering or phishing or vishing.
• Weak or insecure SSL ciphers or certificates.
• Denial of Service (DOS) or Distributed DoS (DDos) attacks.
• Physical attacks against snapWONDERS, its employees or property belonging to us or our employees.
• Physical testing (e.g. office access, open doors, tailgating).
• Attempts to modify or destroy data.
• Posting, transmitting, uploading, linking to, or sending any malware.
• Automated vulnerability scan reports.
• Leverage deceptive techniques.
• Exfiltrating any data under any circumstances.
• Testing third-party websites, applications, or services that integrate with services or products.
• Disclosure of known public files or directories.
• Lack of Secure or HTTP Only flags on non-sensitive cookies.
• Usage of a known vulnerable library or framework without valid attack scenario.
• Actions violate Australian law.

Do not report security vulnerabilities relating to missing security controls or protections that are not directly exploitable. Examples include:

• Weak, insecure, or misconfigured SSL (secure sockets layer) or TLS (transport layer security) certificates.
• Misconfigured DNS (domain name system) records including, but not limited to SPF (sender policy framework) and DMARC (domain-based message authentication reporting and conformance).
• Missing security HTTP (hypertext transfer protocol) headers (for example, permissions policy).
• Theoretical cross-site request forgery and cross-site framing attacks.

This policy applies to only fully snapWONDERS-owned and managed systems and services.

Any service not expressly listed above, such as any connected services, are excluded from scope and are not authorised for testing. Additionally, vulnerabilities found in systems of our vendors fall outside of this policy’s scope and should be reported directly to the vendor in accordance with their disclosure policy (if any). If you aren’t sure whether a system is in scope or not, contact us at [email protected].

Though we may assist in development and maintenance of other internet-accessible systems or services, we ask that active research and testing only be conducted on the systems and services covered by the scope of this policy. If there is a particular system not in scope that you think merits testing, please contact us to discuss it prior to any testing. We will evaluate the scope of this policy over time.

Information submitted under this policy will be used for defensive purposes only – to mitigate or remediate vulnerabilities. If your findings include newly discovered vulnerabilities that affect all users of a product or service and not solely snapWONDERS, we may share your report with the Cybersecurity and Infrastructure Security Agency, where it will be handled under their coordinated vulnerability disclosure process. We will not share your name or contact information without express permission.

We accept vulnerability reports via email and/or secure web form submission:

To help us triage and prioritise 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).
• Be in English, if possible.
• Names of any test accounts you have created (where applicable).
• Your contact details (if you choose).
• Whether you would like public acknowledgement for your contribution (under the acknowledgments section of this webpage), and the name you would like to be acknowledged under.

When you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible.

• Within 5 business days, we will acknowledge that your report has been received.
• 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.
• We will maintain an open dialogue to discuss issues.

Questions regarding this policy may be sent to [email protected] or via our online web form submission. We also invite you to contact us with suggestions for improving this policy.

We list names or aliases of people who have identified and disclosed vulnerabilities to us. The team at snapWONDERS thank you for your support.

• No contributors