Filtered by vendor Openharmony
Subscriptions
Total
45 CVE
CVE | Vendors | Products | Updated | CVSS v3.1 |
---|---|---|---|---|
CVE-2024-45070 | 1 Openharmony | 1 Openharmony | 2025-07-13 | 5.5 Medium |
in OpenHarmony v4.1.2 and prior versions allow a local attacker cause information leak through out-of-bounds Read. | ||||
CVE-2025-20626 | 1 Openharmony | 1 Openharmony | 2025-07-13 | 3.8 Low |
in OpenHarmony v5.0.2 and prior versions allow a local attacker arbitrary code execution in pre-installed apps through use after free. This vulnerability can be exploited only in restricted scenarios. | ||||
CVE-2025-21098 | 1 Openharmony | 1 Openharmony | 2025-07-13 | 5.5 Medium |
in OpenHarmony v5.0.2 and prior versions allow a local attacker cause information leak through out-of-bounds read bypass permission check. | ||||
CVE-2025-22452 | 1 Openharmony | 1 Openharmony | 2025-07-13 | 3.3 Low |
in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through out-of-bounds read. | ||||
CVE-2025-22842 | 1 Openharmony | 1 Openharmony | 2025-07-13 | 3.3 Low |
in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through out-of-bounds read. | ||||
CVE-2025-22847 | 1 Openharmony | 1 Openharmony | 2025-07-13 | 3.3 Low |
in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through out-of-bounds read. | ||||
CVE-2025-23234 | 1 Openharmony | 1 Openharmony | 2025-07-13 | 3.3 Low |
in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through buffer overflow. | ||||
CVE-2025-27534 | 1 Openharmony | 1 Openharmony | 2025-07-13 | 3.3 Low |
in OpenHarmony v5.0.2 and prior versions allow a local attacker case DOS through missing release of memory. | ||||
CVE-2024-47398 | 1 Openharmony | 1 Openharmony | 2025-07-12 | 8.8 High |
in OpenHarmony v4.1.2 and prior versions allow a local attacker cause the device is unable to boot up through out-of-bounds write. | ||||
CVE-2024-54030 | 1 Openharmony | 1 Openharmony | 2025-07-12 | 4.4 Medium |
in OpenHarmony v4.1.2 and prior versions allow a local attacker cause DOS through use after free. | ||||
CVE-2025-20011 | 1 Openharmony | 1 Openharmony | 2025-07-12 | 3.3 Low |
in OpenHarmony v5.0.2 and prior versions allow a local attacker case DOS through missing release of memory. | ||||
CVE-2025-20091 | 1 Openharmony | 1 Openharmony | 2025-07-12 | 3.8 Low |
in OpenHarmony v5.0.2 and prior versions allow a local attacker arbitrary code execution in pre-installed apps through use after free. This vulnerability can be exploited only in restricted scenarios. | ||||
CVE-2025-20102 | 1 Openharmony | 1 Openharmony | 2025-07-12 | 3.3 Low |
in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through out-of-bounds read. | ||||
CVE-2025-21089 | 1 Openharmony | 1 Openharmony | 2025-07-12 | 3.3 Low |
in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through out-of-bounds read. | ||||
CVE-2025-22443 | 1 Openharmony | 1 Openharmony | 2025-07-12 | 3.3 Low |
in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through out-of-bounds read. | ||||
CVE-2025-22837 | 1 Openharmony | 1 Openharmony | 2025-07-12 | 3.3 Low |
in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through NULL pointer dereference. | ||||
CVE-2025-22841 | 1 Openharmony | 1 Openharmony | 2025-07-12 | 3.3 Low |
in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through out-of-bounds read. | ||||
CVE-2025-22851 | 1 Openharmony | 1 Openharmony | 2025-07-12 | 6.5 Medium |
in OpenHarmony v5.0.2 and prior versions allow a local attacker arbitrary code execution in pre-installed apps through integer overflow. | ||||
CVE-2025-22897 | 1 Openharmony | 1 Openharmony | 2025-07-12 | 3.3 Low |
in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through buffer overflow. | ||||
CVE-2025-23240 | 1 Openharmony | 1 Openharmony | 2025-07-12 | 3.8 Low |
in OpenHarmony v5.0.2 and prior versions allow a local attacker arbitrary code execution in pre-installed apps through out-of-bounds write. This vulnerability can be exploited only in restricted scenarios. |