Being a security-focused company, Ory appreciates, encourages, and rewards feedback from the security community. Ory is open source at heart, so feel free to inspect our source code. Ory commits to following HackerOne's vulnerability disclosure guidelines and we ask you to do the same. Thank you for helping keep Ory and our users safe!
While security-testing Ory systems, please make a good-faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Interact only with accounts you own or with the explicit permission of the account holder.
- social engineering like phishing, vishing, or smishing
- security scanning with more than 5 QPS against Ory domains
- any activity that leads to disruption of our service longer than 5 minutes
What can you report
Please report any potential security vulnerability that potentially leads to sensible exploits. Please report vulnerabilities in Ory's upstream dependencies to the respective projects and only reach out to us if the report to upstream was unsuccessful.
When reporting vulnerabilities, please consider the attack scenario, exploitability, and security impact of the bug. Out of scope are attacks
- through the runtime environment of self-hosted Ory installations
- through user-provided configuration like a user not setting appropriate permissions on projects containing sensitive information
- through port address translation for Ory Network Projects
- around missing rate limiting (we have it on our roadmap)
- on intentionally public hosts and information on them like our documentation and website
- that require physical access to the victim's computer
- against vulnerabilities in outdated browsers (more than two versions behind the latest stable version)
- based on software version disclosure, banner identification issues, descriptive error messages or headers (stack traces, application or server errors)
- based on tabnabbing or open redirect unless you can demonstrate an additional security impact
- that require unlikely user interaction
- disclosing configuration and paths unless you include proof of credential leakage or demonstrate an attack with the leaked information (since we manage much of our infrastructure through public GitOps repositories)
Please use Ory's customer support channels if you need help tuning Ory components for security or need help applying security-related updates.
How to report
Submit one vulnerability per report unless you need to chain vulnerabilities to achieve impact.
Please provide a detailed vulnerability report with step-by-step instructions to reproduce the issue. Only vulnerabilities that we can reproduce are eligible for a reward.
Ory commits to these response timelines:
- 1-2 business days to first response
- 3-5 business days from report submission to triage
- 3-5 business days from triage to bounty
We'll stay in close contact with you throughout the process.
While all reward decision are up to our discretion, we generally award these monetary bounties out of our total yearly bounty budget for security vulnerabilities that we can reproduce:
We also award swag for smaller findings like problems with Ory usage of third-party software and services for marketing, email, or developer support.
When receiving multiple reports about the same issue, we award the first report that we can fully reproduce. Multiple vulnerabilities caused by the same underlying issue result in only one bounty. We award public Zero-day vulnerabilities that have had an official patch for less than one month on a case-by-case basis
Please do not discuss any vulnerabilities, even resolved ones, outside this program without written consent from Ory.
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and not result in legal action from Ory against you. If you face legal action in connection with activities conducted under this policy, Ory will take steps to make it known that you conducted your actions in compliance with this policy.