Report a vulnerability
How to report a vulnerability affecting Kilo or Chirp software, what to include, and the boundaries for safe research.
We welcome reports of security vulnerabilities in our products and services, and we will work with you to understand and resolve the issue.
Contact: info [at] kiloiot.de (replace [at] with @)
Please include, as far as you can: the affected product and version, a description of the issue, the steps to reproduce it, and the impact you believe it has. If you have a preferred name for credit, tell us.
Scope
This policy covers software and services supplied or operated by CHIRP USA LLC, including the Kilo/Chirp platform and IoT Alerts. Reports about another artifact are accepted and triaged, but this policy does not claim that CHIRP USA LLC manufactures or supplies an artifact whose entity role has not been established.
What we ask
Please give us a reasonable opportunity to fix an issue before disclosing it publicly. While investigating, please do not access, modify or delete data belonging to others, degrade our services, or use social engineering, phishing or physical attacks against our people or infrastructure. Test only against your own account or your own deployment.
This policy does not authorize access to systems or data and does not create a bug-bounty, payment, safe-harbour, non-enforcement or immunity commitment.
How we will respond
We will receive and assess reports through the contact channel. No acknowledgement, response, remediation, disclosure, support or credit deadline is promised by this policy.
Credit
Do not include sensitive personal data in a report. We will minimize reporter information and handle it under the applicable privacy and evidence procedures.
Our regulatory obligations
Depending on the affected product, responsible company and event, applicable law may require the accountable manufacturer or other obligated subject to report through the relevant regulatory route. We will protect sensitive information and coordinate legally required reporting and user communication.
Last updated