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

cve-report_en.md 4.9 kB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071
  1. # MindSpore Security
  2. MindSpore is a training and inference framework that supports device, edge, and cloud scenarios. It is widely used in various fields, such as terminals, edge computing, cloud services, network devices, storage devices, and 5G, and needs to meet application security requirements in preceding scenarios.
  3. As a general-purpose computing framework, MindSpore can run on different chip platforms such as the CPU, GPU, and Ascend. Users provide data or models as the input and obtain training models or inference results. As core assets in the AI field, data and models are necessary for continuous security protection of AI systems.
  4. We also provide suggestions on secure running of key components:
  5. + [MindSpore Security Usage Suggestions](https://gitee.com/mindspore/mindspore/blob/master/SECURITY.md)
  6. + [MindInsight Security Usage Suggestions](https://gitee.com/mindspore/mindinsight/blob/master/SECURITY.md)
  7. To build a more secure AI framework, we sincerely invite you to join us.
  8. ## How to Report Security Issues to the MindSpore Community
  9. If you find a suspected security issue, use [Suspected Security Issue Reporting Template](https://gitee.com/mindspore/community/blob/master/security/template/report-template_en.md) to report it so that the community vulnerability management team (VMT) is able to confirm and fix the issue as soon as possible with sufficient details. Your email will be confirmed within one working day. Within seven days, we will provide more detailed replies to your suspected security issues and provide the next-step handling policy.
  10. To ensure security, please use the PGP public key to encrypt your email before sending it.
  11. + Security email address: <mindspore-security@mindspore.cn>
  12. + PGP public key:
  13. ```
  14. -----BEGIN PGP PUBLIC KEY BLOCK-----
  15. iQG2BCABCgAgFiEEwUbNw8zaTIe27U8lt42TVbzPfREFAl58v18CHQAACgkQt42T
  16. VbzPfRGVswwAnSIi1fE0CzIkxPrhfcnfF+vx5y+qpk6ssFr5iFuepBSbA+ZGhaDn
  17. ULYOkBMnGfrgzjw8OzMK7vKIgR2ymmuTJt9qpFH4OIXRX1OXoMYnkPxrQJFpNZpP
  18. BvnxmEey0VOvz9Y3Fa4mHMjvA3I2pbSlH+T2wkGQRO5zhKN7NhQfRFgyFNQT2l5m
  19. pPBdm+sAs5ty6eQuSZF1wECIW17WB53o171DTNbAPySEfOLvq0orNAJWjT4sR1jn
  20. 9M20t3DpjC5dZuMCUuZTbCgHkaLOo0ZkwMXV+dPkm/4hMWLVPxRvlkH02PI++KBl
  21. N8cW+TZb1YN/va9Nrjh+Ah50Px2nmQ/fk60VHKj5hTb8U+PSPGlvWUALwb6ckm55
  22. nUcBvFiDpe7uAtX88sv2kBR6gIbr0pW9JwOnBLjxGoM3lgfrIot1qFWdBGJrRnIo
  23. bgMtm0PEcwRfHefJY//4BiDgg2ef9DIX7VSSb6rV0HJpNz0IAxyzG41BdSG+3dSb
  24. ns0y2L0F2M+N
  25. =HPa4
  26. -----END PGP PUBLIC KEY BLOCK-----
  27. ```
  28. ## MindSpore Community Security Issue Disclosure Process
  29. After receiving the issues, we will handle the security issues according to the following process:
  30. + After receiving suspected security issues, the vulnerability management team (VMT) immediately confirms the integrity of reported information and issue severity.
  31. + Organize community teams to carry out technical analysis, confirm issue details, and provide analysis reports.
  32. + Confirm the vulnerability and apply for CVE, communicate with the vulnerability reporter about the issue, align the subsequent fixing and release plan, and prepare the security advisory (SA).
  33. + Complete vulnerability patch development/verification and initiate restricted disclosure.
  34. + Publicly release patches and security advisory (SA).
  35. ## MindSpore Community Vulnerability Management Team (VMT)
  36. The VMT consists of vulnerability management experts in the community. The team is responsible for coordinating the entire process from vulnerability receiving to disclosure, including:
  37. + Vulnerability collection: Suspected security vulnerabilities discovered by community members and external researchers can be reported to the VMT through <mindspore-security@mindspore.cn>.
  38. + Vulnerability tracking and handling: The VMT will record the confirmed vulnerabilities in the MindSpore community, confirm and fix the vulnerabilities, and keep effective communication with the reporter during the process.
  39. + Responsible disclosure: After vulnerabilities are properly fixed, the VMT will release vulnerability information to the community in the form of SA.
  40. ## MindSpore Security Advisory (SA)
  41. None
  42. ## MindSpore Security Note (SN)
  43. + Some vulnerabilities of third-party open-source components need to be fixed by users.
  44. + Python 3.7.5 has the following vulnerabilities:
  45. + [CVE-2019-18348](https://nvd.nist.gov/vuln/detail/CVE-2019-18348)
  46. + [CVE-2020-8315](https://nvd.nist.gov/vuln/detail/CVE-2020-8315)
  47. + [CVE-2020-8492](https://nvd.nist.gov/vuln/detail/CVE-2020-8492)
  48. + Pillow 6.2.0 has the following vulnerabilities:
  49. + [CVE-2019-19911](https://nvd.nist.gov/vuln/detail/CVE-2019-19911)
  50. + [CVE-2020-5310](https://nvd.nist.gov/vuln/detail/CVE-2020-5310)
  51. + [CVE-2020-5311](https://nvd.nist.gov/vuln/detail/CVE-2020-5311)
  52. + [CVE-2020-5312](https://nvd.nist.gov/vuln/detail/CVE-2020-5312)
  53. + [CVE-2020-5313](https://nvd.nist.gov/vuln/detail/CVE-2020-5313)

社区治理架构的内容详见governance.md,该提案处于初稿阶段,后期可能会在 技术指导委员会(TSC)的许可下进行刷新。除此之外,社区还提供了特别兴趣小组(SIG) 和工作组(Working Group)的资料介绍。

Contributors (1)