blob: e43c5642f9b570673e792e773da180a773517273 [file] [log] [blame] [view]
David Brown0d98a9c2019-10-02 13:59:42 -06001# MCUboot project security policy
2
3## Reporting Security Issues
4
5The MCUboot team takes security, vulnerabilities, and weaknesses
6seriously.
7
8Security issues should be sent to the current maintainers of the
9project:
10
11- David Brown: davidb@davidb.org or david.brown@linaro.org
12- Fabio Utzig: utzig@apache.org
13
14 pub rsa4096 2011-10-14 [SC]
15 DAFD760825AE2636AEA9CB19E6BA9F5C5E54DF82
16 uid [ultimate] David Brown <davidb@davidb.org>
17 uid [ultimate] David Brown <david.brown@linaro.org>
18 sub rsa4096 2011-10-14 [E]
19
20and
21
22 pub rsa4096 2017-07-28 [SC]
23 126087C7E725625BC7E89CC7537097EDFD4A7339
24 uid [ unknown] Fabio Utzig <utzig@apache.org>
25 uid [ unknown] Fabio Utzig <utzig@utzig.org>
26 sub rsa4096 2017-07-28 [E]
27
28Please include the word "SECURITY" as well as "MCUboot" in the subject
29of any messages.
30
31We will make our best effort to respond within a timely manner. Most
32vulnerabilities found within published code will undergo an embargo of
3390 days to allow time fixes to be developed and deployed.
34
35## Vulnerability Advisories
36
37Vulnerability reports and published fixes will be reported as follows:
38
39- Issues will be entered into Github's [Security Advisory
40 system](https://github.com/JuulLabs-OSS/mcuboot/security/advisories), with
41 the interested parties (including the reporter) added as viewers.
42
43- The release notes will contain a reference to any allocated CVE(s).
44
45- When any embargo is lifted, the Security Advisory page will be made
46 public, and the public CVE database will be updated with all
47 relevant information.