1# Security Policy 2 3 4## How to report a security vulnerability 5 6This describes how you can report an OpenBMC security vulnerability 7privately to give the project time to address the problem before 8public disclosure. 9 10The main ideas are: 11 - You have information about a security problem which is not yet 12 publicly available. 13 - You want the problem fixed before public disclosure and 14 you are willing to help make that happen. 15 - You understand the problem will eventually be publicly disclosed. 16 17To begin the process: 18 - Send an email to `openbmc-security at lists.ozlabs.org` with details 19 about the security problem such as: 20 - the version and configuration of OpenBMC the problem appears in 21 - how to reproduce the problem 22 - what are the symptoms 23 - As the problem reporter, you will be included in the email thread 24 for the problem. 25 26The OpenBMC security response team (SRT) will respond to you and work to 27address the problem. Activities may include: 28 - Privately engage community members to understand and address the 29 problem. Anyone brought onboard should be given a link to the 30 OpenBMC [security response team guidelines][]. 31 - Work to determine the scope and severity of the problem, 32 such as [CVSS metrics][]. 33 - Work to create or identify an existing [CVE][]. 34 - Coordinate workarounds and fixes with you and the community. 35 - Coordinate announcement details with you, such as timing or 36 how you want to be credited. 37 - Create an OpenBMC security advisory. 38 39Please refer to the [CERT Guide to Coordinated Vulnerability Disclosure][], 40(SPECIAL REPORT CMU/SEI-2017-SR-022) for additional considerations. 41 42Alternatives to this process: 43 - If the problem is not severe, please write an issue to the affected 44 repository or email the list. 45 - Join the OpenBMC community and fix the problem yourself. 46 - If you are unsure if the error is in OpenBMC (contrasted with 47 upstream projects such as the Linux kernel or downstream projects 48 such as a customized version of OpenBMC), please report it and we 49 will help you route it to the correct area. 50 - Discuss your topic in other [OpenBMC communication channels](https://github.com/openbmc/openbmc). 51 52[security response team guidelines]: ./obmc-security-response-team-guidelines.md 53[CVSS metrics]: https://www.first.org/cvss/calculator/3.0 54[CVE]: http://cve.mitre.org/about/index.html 55[CERT Guide to Coordinated Vulnerability Disclosure]: https://resources.sei.cmu.edu/asset_files/SpecialReport/2017_003_001_503340.pdf 56