Vulnerability Submission Form
Last updated: 5/31/2022
Nest Health Tech Inc. ("Nest") looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.
Your participation in the Bug Bounty Program (“Program”) is voluntary and subject to the terms and conditions set forth in this Nest Bug Bounty Program Policy (the “Policy”), and any other agreement in which you have entered with Nest in connection with the Program (collectively “Nest Health Tech Inc. Agreements”). By submitting a vulnerability to Nest, you acknowledge that you have read and agreed to this Policy and the Nest Health Tech Inc. Agreements.
Nest maintains the right to terminate this Bug Bounty Program (“Program”) at any time with or without notice. Nest may amend this Policy at any time. By continuing to participate in the Program after any such changes, you accept the Policy’s terms and conditions, as modified.
Nest may, in its sole discretion, remove you from the Program, or disqualify you from receiving any benefit of the Program, if you breach this Policy or any of the Program’s terms, or if Nest determines that your participation in the Program could adversely affect Nest, our affiliates, subsidiaries, customers, employees or agents.
Nest will make a best effort to meet the following SLAs for hackers participating in our program:
SLA in business days
- First Response - 2 business days
- Time to Triage - 2 business days
- Time to Resolution - depends on severity and complexity
- As this is a private program, please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
- Follow HackerOne's disclosure guidelines.
- Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged.
- Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
- When duplicates occur, we only triage the first report that was received (provided that it can be fully reproduced).
- Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.
- Social engineering (e.g. phishing, vishing, smishing) is prohibited.
- Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
- To be eligible for the Bug Bounty Program, you must not:
- Be a resident of, or make your submission from, a country against which the United States has issued export sanctions or other trade restrictions (e.g., Cuba, Iran, North Korea, Sudan, and Syria).
- Be in violation of any national, state, or local law or regulation.
- Be a current employee of Nest or its affiliates or subsidiaries, or an employee who has left Nest, or its affiliates or subsidiaries within the past 12 months.
- Be an immediate family member of a person employed by Nest or its subsidiaries or affiliates; or
- Be less than 13 years of age. If you are between the ages of 13 - 17 years old but are considered a minor in your place of residence, you must get your parent’s or legal guardian’s permission prior to participating in the program.
Out of Scope Vulnerabilities
When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:
- Clickjacking on pages with no sensitive actions
- Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
- Attacks requiring MITM or physical access to a user's device.
- Previously known vulnerable libraries without a working Proof of Concept.
- Comma Separated Values (CSV) injection without demonstrating a vulnerability.
- Missing best practices in SSL/TLS configuration.
- Any activity that could lead to the disruption of our service (DoS).
- Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
- Rate limiting or bruteforce issues on non-authentication endpoints
- Missing best practices in Content Security Policy.
- Missing HttpOnly or Secure flags on cookies
- Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
- Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
- Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
- Open redirect - unless an additional security impact can be demonstrated
- Issues that require unlikely user interaction
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.
Thank you for helping keep Nest and our users safe!
Submit Vulnerability Report
Send the vulnerability report to email@example.com with the following template::
[add the attack surface of this issue]
[add the type of the potential issue you have discovered]
[add summary of the vulnerability]
## Steps To Reproduce:
[add details for how we can reproduce the issue]
1. [add step]
1. [add step]
1. [add step]
## Supporting Material/References:
[list any additional material (e.g. screenshots, logs, etc.)]
* [attachment / reference]