You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

SECURITY.md 2.9KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364
  1. # Security Policy
  2. [Security](https://nextcloud.com/security/) is very important to us.
  3. If you believe you have found a security vulnerability that meets our definition of a security
  4. vulnerability, please report is as described below.
  5. ## Context
  6. Please review our [threat model and accepted risks](https://nextcloud.com/security/threat-model) to learn what
  7. is currently considered a security vulnerability versus expected behavior. And review what is considered
  8. [in scope or bounty eligible](https://hackerone.com/nextcloud/policy_scopes).
  9. ## Reporting a Vulnerability
  10. ** **Please do _not_ report security vulnerabilities through public GitHub issues.** **
  11. If you have discovered a security matter with Nextcloud, please read our
  12. [responsible disclosure guidelines](https://nextcloud.com/security/) and contact us at
  13. [hackerone.com/nextcloud](https://hackerone.com/nextcloud).
  14. Your report should include:
  15. - Product version
  16. - A vulnerability description
  17. - Reproduction steps
  18. - Any other details you think are likely to be important
  19. ### What to Expect
  20. You should receive an initial acknowledgement within 24 hours in most cases.
  21. A member of the security team will confirm the vulnerability, determine its impact, follow-up with any questions,
  22. and coordinate the fix and publication.
  23. The fix will be applied to all applicable and still supported stable branches, tested, and packaged in the next security release.
  24. The vulnerability will be publicly announced after the release. Finally, your name will be added
  25. to the [hall of fame](https://hackerone.com/nextcloud/thanks) as a thank you from the entire Nextcloud
  26. community.
  27. If the vulnerability involves an app that is not maintained by Nextcloud (i.e. hosted by the
  28. Nextcloud project but community maintained, or hosted elsewhere), the security team will try to coordinate with the
  29. current maintainer and help to get the issue fixed in similar fashion.
  30. ### Bug Bounties
  31. If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Details
  32. on past bounty ranges can be found at [hackerone.com/nextcloud](https://hackerone.com/nextcloud).
  33. ## Existing Security Advisories
  34. Published security advisories for the Nextcloud Server, Clients and Apps can be viewed at
  35. [https://github.com/nextcloud/security-advisories/security/advisories](https://github.com/nextcloud/security-advisories/security/advisories).
  36. ## Supported Versions
  37. Nextcloud Server major release versions are being supported with security updates for 1 year after their initial release.
  38. Please visit https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule for further details.
  39. ## Additional Information
  40. Please visit [https://nextcloud.com/security/](https://nextcloud.com/security/) for further information about Nextcloud security.
  41. Please visit [https://nextcloud.com/security/threat-model](https://nextcloud.com/security/threat-model) for our threat model and accepted risks.