# MindSpore Security 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. 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. We also provide suggestions on secure running of key components: + [MindSpore Security Usage Suggestions](https://gitee.com/mindspore/mindspore/blob/master/SECURITY.md) + [MindInsight Security Usage Suggestions](https://gitee.com/mindspore/mindinsight/blob/master/SECURITY.md) To build a more secure AI framework, we sincerely invite you to join us. ## How to Report Security Issues to the MindSpore Community 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. To ensure security, please use the PGP public key to encrypt your email before sending it. + Security email address: + PGP public key: ``` -----BEGIN PGP PUBLIC KEY BLOCK----- iQG2BCABCgAgFiEEwUbNw8zaTIe27U8lt42TVbzPfREFAl58v18CHQAACgkQt42T VbzPfRGVswwAnSIi1fE0CzIkxPrhfcnfF+vx5y+qpk6ssFr5iFuepBSbA+ZGhaDn ULYOkBMnGfrgzjw8OzMK7vKIgR2ymmuTJt9qpFH4OIXRX1OXoMYnkPxrQJFpNZpP BvnxmEey0VOvz9Y3Fa4mHMjvA3I2pbSlH+T2wkGQRO5zhKN7NhQfRFgyFNQT2l5m pPBdm+sAs5ty6eQuSZF1wECIW17WB53o171DTNbAPySEfOLvq0orNAJWjT4sR1jn 9M20t3DpjC5dZuMCUuZTbCgHkaLOo0ZkwMXV+dPkm/4hMWLVPxRvlkH02PI++KBl N8cW+TZb1YN/va9Nrjh+Ah50Px2nmQ/fk60VHKj5hTb8U+PSPGlvWUALwb6ckm55 nUcBvFiDpe7uAtX88sv2kBR6gIbr0pW9JwOnBLjxGoM3lgfrIot1qFWdBGJrRnIo bgMtm0PEcwRfHefJY//4BiDgg2ef9DIX7VSSb6rV0HJpNz0IAxyzG41BdSG+3dSb ns0y2L0F2M+N =HPa4 -----END PGP PUBLIC KEY BLOCK----- ``` ## MindSpore Community Security Issue Disclosure Process After receiving the issues, we will handle the security issues according to the following process: + After receiving suspected security issues, the vulnerability management team (VMT) immediately confirms the integrity of reported information and issue severity. + Organize community teams to carry out technical analysis, confirm issue details, and provide analysis reports. + 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). + Complete vulnerability patch development/verification and initiate restricted disclosure. + Publicly release patches and security advisory (SA). ## MindSpore Community Vulnerability Management Team (VMT) 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: + Vulnerability collection: Suspected security vulnerabilities discovered by community members and external researchers can be reported to the VMT through . + 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. + Responsible disclosure: After vulnerabilities are properly fixed, the VMT will release vulnerability information to the community in the form of SA. ## MindSpore Security Advisory (SA) None ## MindSpore Security Note (SN) + Some vulnerabilities of third-party open-source components need to be fixed by users. + Python 3.7.5 has the following vulnerabilities: + [CVE-2019-18348](https://nvd.nist.gov/vuln/detail/CVE-2019-18348) + [CVE-2020-8315](https://nvd.nist.gov/vuln/detail/CVE-2020-8315) + [CVE-2020-8492](https://nvd.nist.gov/vuln/detail/CVE-2020-8492) + Pillow 6.2.0 has the following vulnerabilities: + [CVE-2019-19911](https://nvd.nist.gov/vuln/detail/CVE-2019-19911) + [CVE-2020-5310](https://nvd.nist.gov/vuln/detail/CVE-2020-5310) + [CVE-2020-5311](https://nvd.nist.gov/vuln/detail/CVE-2020-5311) + [CVE-2020-5312](https://nvd.nist.gov/vuln/detail/CVE-2020-5312) + [CVE-2020-5313](https://nvd.nist.gov/vuln/detail/CVE-2020-5313)