代码拉取完成，页面将自动刷新
published January 3,2023
updated January 3,2023
| Vulnerability ID | related Vulnerability | Vulnerability Description | Vulnerability Impact | CVSS3.1 Base Score | affected versions | affected projects | fix link | reference |
|---|---|---|---|---|---|---|---|---|
| OpenHarmony-SA-2023-0101 | CVE-2023-0035 | softbus_client_stub in communication subsystem has an authentication bypass vulnerability which allows an "SA relay attack". | Local attackers can bypass authentication and attack other SAs with high privilege. | 6.5 | OpenHarmony-v3.0-LTS through OpenHarmony-v3.0.5-LTS | communication_dsoftbus | 3.0.x | Reported by OpenHarmony Team |
| OpenHarmony-SA-2023-0102 | CVE-2023-0036 | platform_callback_stub in misc subsystem has an authentication bypass vulnerability which allows an "SA relay attack". | Local attackers can bypass authentication and attack other SAs with high privilege. | 6.5 | OpenHarmony-v3.0-LTS through OpenHarmony-v3.0.5-LTS | inputmethod_imf | 3.0.x | Reported by OpenHarmony Team |
| CVE | severity | affected OpenHarmony versions | fix link |
|---|---|---|---|
| CVE-2021-3782 | Critical | OpenHarmony-v3.0-LTS through OpenHarmony-v3.0.6-LTS | 3.0.x |
| CVE-2022-3046 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.3-Release | 3.1.x |
| CVE-2022-3041 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.3-Release | 3.1.x |
| CVE-2022-3040 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.3-Release | 3.1.x |
| CVE-2022-3039 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.3-Release | 3.1.x |
| CVE-2022-3038 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.3-Release | 3.1.x |
| CVE-2022-3057 | Medium | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.3-Release | 3.1.x |
| CVE-2022-3195 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.3-Release | 3.1.x |
| CVE-2022-3054 | Medium | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.3-Release | 3.1.x |
| CVE-2022-3075 | Critical | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.3-Release | 3.1.x |
| CVE-2022-3373 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release | 3.1.x |
| CVE-2022-3370 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release | 3.1.x |
| CVE-2022-3311 | Medium | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release | 3.1.x |
| CVE-2022-3316 | Medium | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release | 3.1.x |
| CVE-2022-3315 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release | 3.1.x |
| CVE-2022-3304 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release | 3.1.x |
| CVE-2022-43680 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.3-Release OpenHarmony-v3.0-LTS through OpenHarmony-v3.0.6-LTS |
3.1.x 3.0.x |
| CVE-2022-32221 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release OpenHarmony-v3.0-LTS through OpenHarmony-v3.0.6-LTS |
3.1.x 3.0.x |
| CVE-2022-42916 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release OpenHarmony-v3.0-LTS through OpenHarmony-v3.0.6-LTS |
3.1.x 3.0.x |
| CVE-2022-42915 | Critical | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release OpenHarmony-v3.0-LTS through OpenHarmony-v3.0.6-LTS |
3.1.x 3.0.x |
| CVE-2022-44638 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release OpenHarmony-v3.0-LTS through OpenHarmony-v3.0.7-LTS |
3.1.x 3.0.x |
| CVE-2022-40284 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release | 3.1.x |
| CVE-2022-40303 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release OpenHarmony-v3.0-LTS through OpenHarmony-v3.0.7-LTS |
3.1.x 3.0.x |
| CVE-2022-40304 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release OpenHarmony-v3.0-LTS through OpenHarmony-v3.0.7-LTS |
3.1.x 3.0.x |
| CVE-2022-37454 | Critical | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release | 3.1.x |
| CVE-2022-42919 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release | 3.1.x |
| CVE-2022-45061 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release | 3.1.x |
| CVE-2020-10735 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.3-Release | 3.1.x |
| CVE-2022-3169 | Medium | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release OpenHarmony-v3.0-LTS through OpenHarmony-v3.0.7-LTS |
3.1.x 3.0.x |
| CVE-2022-42895 | Medium | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release OpenHarmony-v3.0-LTS through OpenHarmony-v3.0.7-LTS |
3.1.x 3.0.x |
| CVE-2022-42896 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release OpenHarmony-v3.0-LTS through OpenHarmony-v3.0.7-LTS |
3.1.x 3.0.x |
| CVE-2022-41858 | Medium | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release OpenHarmony-v3.0-LTS through OpenHarmony-v3.0.7-LTS |
3.1.x 3.0.x |
| CVE-2022-45934 | Medium | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release OpenHarmony-v3.0-LTS through OpenHarmony-v3.0.7-LTS |
3.1.x 3.0.x |
| CVE-2022-4139 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release OpenHarmony-v3.0-LTS through OpenHarmony-v3.0.7-LTS |
3.1.x 3.0.x |
| CVE-2022-20566 | Low | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release OpenHarmony-v3.0-LTS through OpenHarmony-v3.0.7-LTS |
3.1.x 3.0.x |
| CVE-2022-4378 | High | OpenHarmony-v3.1-Release through OpenHarmony-v3.1.4-Release OpenHarmony-v3.0-LTS through OpenHarmony-v3.0.7-LTS |
3.1.x 3.0.x |
此处可能存在不合适展示的内容，页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容，可点击提交进行申诉，我们将尽快为您处理。
