Vulnerabilities (CVE)

Filtered by vendor Openatom Subscribe
Total 124 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2025-20063 1 Openatom 1 Openharmony 2025-06-09 N/A 3.3 LOW
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause apps crash through type confusion.
CVE-2025-21082 1 Openatom 1 Openharmony 2025-06-09 N/A 3.3 LOW
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause apps crash through type confusion.
CVE-2025-23235 1 Openatom 1 Openharmony 2025-06-09 N/A 3.3 LOW
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause DOS through out-of-bounds read.
CVE-2025-24493 1 Openatom 1 Openharmony 2025-06-09 N/A 5.5 MEDIUM
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through race condition.
CVE-2025-25217 1 Openatom 1 Openharmony 2025-06-09 N/A 3.3 LOW
in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through NULL pointer dereference.
CVE-2025-26691 1 Openatom 1 Openharmony 2025-06-09 N/A 5.5 MEDIUM
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through get permission.
CVE-2025-26693 1 Openatom 1 Openharmony 2025-06-09 N/A 3.3 LOW
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through get permission.
CVE-2025-27131 1 Openatom 1 Openharmony 2025-06-09 N/A 6.1 MEDIUM
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause DOS through improper input.
CVE-2025-27242 1 Openatom 1 Openharmony 2025-06-09 N/A 3.3 LOW
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause DOS through improper input.
CVE-2025-27247 1 Openatom 1 Openharmony 2025-06-09 N/A 5.5 MEDIUM
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through get permission.
CVE-2025-27563 1 Openatom 1 Openharmony 2025-06-09 N/A 3.3 LOW
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through get permission.
CVE-2025-27132 1 Openatom 1 Openharmony 2025-05-09 N/A 3.8 LOW
in OpenHarmony v5.0.3 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.
CVE-2025-27241 1 Openatom 1 Openharmony 2025-05-09 N/A 3.3 LOW
in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through NULL pointer dereference.
CVE-2025-27248 1 Openatom 1 Openharmony 2025-05-09 N/A 3.3 LOW
in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through NULL pointer dereference.
CVE-2025-22886 1 Openatom 1 Openharmony 2025-05-09 N/A 3.3 LOW
in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through missing release of memory.
CVE-2025-25052 1 Openatom 1 Openharmony 2025-05-09 N/A 3.3 LOW
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause DOS through buffer overflow.
CVE-2025-25218 1 Openatom 1 Openharmony 2025-05-09 N/A 3.3 LOW
in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through NULL pointer dereference.
CVE-2021-33645 3 Fedoraproject, Feep, Openatom 3 Fedora, Libtar, Openeuler 2025-04-02 N/A 7.5 HIGH
The th_read() function doesn’t free a variable t->th_buf.gnu_longlink after allocating memory, which may cause a memory leak.
CVE-2021-33643 3 Fedoraproject, Feep, Openatom 3 Fedora, Libtar, Openeuler 2025-04-02 N/A 9.1 CRITICAL
An attacker who submits a crafted tar file with size in header struct being 0 may be able to trigger an calling of malloc(0) for a variable gnu_longlink, causing an out-of-bounds read.
CVE-2021-33640 2 Fedoraproject, Openatom 2 Fedora, Openeuler 2025-04-02 N/A 6.2 MEDIUM
After tar_close(), libtar.c releases the memory pointed to by pointer t. After tar_close() is called in the list() function, it continues to use pointer t: free_longlink_longname(t->th_buf) . As a result, the released memory is used (use-after-free).