|
4 | 4 | -->
|
5 | 5 | # Security Policy
|
6 | 6 |
|
7 |
| -## Supported Versions |
| 7 | +# 💡 TLDR: Report issues at [hackerone.com/nextcloud](https://hackerone.com/nextcloud) |
| 8 | + |
| 9 | +# Security Policy |
| 10 | + |
| 11 | +[Security](https://nextcloud.com/security/) is very important to us. |
| 12 | + |
| 13 | +If you believe you have found a security vulnerability that meets our definition of a security |
| 14 | +vulnerability, please report is as described below. |
| 15 | + |
| 16 | +## Context |
| 17 | + |
| 18 | +Please review our [threat model and accepted risks](https://nextcloud.com/security/threat-model) to learn what |
| 19 | +is currently considered a security vulnerability versus expected behavior. And review what is considered |
| 20 | +[in scope or bounty eligible](https://hackerone.com/nextcloud/policy_scopes). |
8 | 21 |
|
9 |
| -Only the latest version is supported. We release every second month a feature release (currently 3.x) and inbetween a bug fix release (3.x.y). |
10 | 22 |
|
11 | 23 | ## Reporting a Vulnerability
|
12 | 24 |
|
13 |
| -Security is very important to us. If you have discovered a security issue with Nextcloud, |
14 |
| -please read our responsible disclosure guidelines and contact us at [hackerone.com/nextcloud](https://hackerone.com/nextcloud). |
| 25 | +**⚠️ Please do _not_ report security vulnerabilities through public GitHub issues.** |
| 26 | + |
| 27 | +If you have discovered a security matter with Nextcloud, please read our |
| 28 | +[responsible disclosure guidelines](https://nextcloud.com/security/) and contact us at |
| 29 | +[hackerone.com/nextcloud](https://hackerone.com/nextcloud). |
| 30 | + |
15 | 31 | Your report should include:
|
16 | 32 |
|
17 | 33 | - Product version
|
18 | 34 | - A vulnerability description
|
19 | 35 | - Reproduction steps
|
| 36 | +- Any other details you think are likely to be important |
| 37 | + |
| 38 | +### What to Expect |
20 | 39 |
|
21 |
| -A member of the security team will confirm the vulnerability, determine its impact, and develop a fix. |
22 |
| -The fix will be applied to the master branch, tested, and packaged in the next bug fix release. |
| 40 | +You should receive an initial acknowledgement within 24 hours in most cases. |
| 41 | + |
| 42 | +A member of the security team will confirm the vulnerability, determine its impact, follow-up with any questions, |
| 43 | +and coordinate the fix and publication. |
| 44 | + |
| 45 | +The fix will be applied to all applicable and still supported stable branches, tested, and packaged in the next security release. |
23 | 46 | The vulnerability will be publicly announced after the release. Finally, your name will be added
|
24 |
| -to the [hall of fame](https://hackerone.com/nextcloud/thanks) as a thank you from the entire Nextcloud community. Note our |
25 |
| -[threat model](https://nextcloud.com/security/threat-model) to know what is expected behavior. |
| 47 | +to the [hall of fame](https://hackerone.com/nextcloud/thanks) as a thank you from the entire Nextcloud |
| 48 | +community. |
| 49 | + |
| 50 | +If the vulnerability involves an app that is not maintained by Nextcloud (i.e. hosted by the |
| 51 | +Nextcloud project but community maintained, or hosted elsewhere), the security team will try to coordinate with the |
| 52 | +current maintainer and help to get the issue fixed in similar fashion. |
| 53 | + |
| 54 | +### Bug Bounties |
| 55 | + |
| 56 | +If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Details |
| 57 | +on past bounty ranges can be found at [hackerone.com/nextcloud](https://hackerone.com/nextcloud). |
| 58 | + |
| 59 | +## Existing Security Advisories |
| 60 | + |
| 61 | +Published security advisories for the Nextcloud Server, Clients and Apps can be viewed at |
| 62 | +[https://github.com/nextcloud/security-advisories/security/advisories](https://github.com/nextcloud/security-advisories/security/advisories). |
| 63 | + |
| 64 | +## Supported Versions |
| 65 | + |
| 66 | +Only the latest version is supported. We release every second month a feature release (currently 3.x) and inbetween a bug fix release (3.x.y). |
26 | 67 |
|
| 68 | +## Additional Information |
27 | 69 |
|
28 |
| -Please visit https://nextcloud.com/security/ for further information about security. |
| 70 | +Please visit [https://nextcloud.com/security/](https://nextcloud.com/security/) for further information about Nextcloud security. |
| 71 | +Please visit [https://nextcloud.com/security/threat-model](https://nextcloud.com/security/threat-model) for our threat model and accepted risks. |
0 commit comments