Impinj connects billions of everyday items such as apparel, medical supplies, food and luggage to applications such as inventory management, asset tracking and item authentication, delivering real-time information to businesses about items they create, manage, transport and sell. The Impinj Platform wirelessly delivers information about these items’ unique identity, location and authenticity (what we call Item Intelligence). Impinj looks forward to working with the security community to find security vulnerabilities in order to keep our businesses and customers safe.

Response Times

Impinj will make a best effort to meet the following Response Times for hackers participating in our program:

• Time to first response (from report submit) - 2 business days
• Time to triage (from report submit) - 2 business days

We’ll try to keep you informed about our progress throughout the process. Please note that response times are in business days.

Disclosure Policy

• Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program.
• Follow HackerOne's disclosure guidelines __.

Program Rules

• Please provide detailed reports with reproducible steps.
• Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
• 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.

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.
• Unauthenticated/logout/login CSRF.
• 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

Thank you for helping keep Impinj and our users safe!