submit bug report: https://www.owncloud.comWe created the ownCloud Security Bug Bounty Program to reward security researchers for finding issues in the ownCloud Server, and in so doing help strengthen ownCloud Server for customers, users and the community.
Rewards
If the bug is identified as meaningful and qualifies for the program, and the reporter has followed the Disclosure Policy, the bug bounty is paid out on the following schedule by bug severity:
Impact Definition Reward
Critical Gaining remote code execution on the server as a non-admin user. (i.e. RCE) $5000
High Gaining access to complete user data of any other user. (i.e. Auth Bypass) or SQL Injection with critical effects $2000
Medium Allowing the adversary to gain complete control over a single user session. (Stored XSS with CSP bypass / Critical CSRF / …) $500
Low Vulnerabilities that can only be exploited in very rare cases or have marginal impact. (High amount of unlikely user interaction / …) $50
The severity of the bug is determined at the discretion of ownCloud and the ownCloud security team.
All bounties will be paid using the HackerOne platform, a site that manages bug bounty payouts and security contacts for software vendors.
Disclosure Policy
Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.
Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.
Only test for vulnerabilities on your own installation of ownCloud server, desktop or related mobile applications.
Do not publish information related to the vulnerability until ownCloud has made an announcement to the community.
In case of duplicate reports we only reward the first reporter of the vulnerability. Public disclosure prior to resolution and without explicit confirmation by the ownCloud Security Team will result in disqualification for the bounty program.
We believe in transparency and will publicly disclose each applicable report.
Note that we consider any bug caused by an already known and fixed PHP issues as a non-issue. This means that you should always test using the latest available PHP release (of the 5.5, 5.6 or 7.0 branch) running on mod_php.
Found a bug in one of our websites or so? While we can't offer you any monetary reward we will acknowledge the issue and happily accept reports for it via this platform as well. But please do not run any Denial of Service attacks against our infrastructure or extract user data. Please do also refrain from using automated testing tools against our infrastructure.
