in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through missing release of memory.

in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through missing release of memory.

in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through missing release of memory.

in OpenHarmony v5.0.2 and prior versions allow a local attacker case DOS through missing release of memory.

in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through missing release of memory.

in OpenHarmony v4.1.0 and prior versions allow a local attacker cause DOS by memory leak.

in OpenHarmony v4.1.0 and prior versions allow a local attacker cause crash through integer overflow.

in OpenHarmony v3.2.4 and prior versions allow a local attacker cause apps crash through type confusion.

in OpenHarmony v4.0.0 and prior versions allow a local attacker cause DOS through use after free.

in OpenHarmony v3.2.2 and prior versions allow a local attacker cause multimedia audio crash through modify a released pointer.

in OpenHarmony v5.0.3 and prior versions allow a local attacker cause DOS through improper input.

in OpenHarmony v5.0.3 and prior versions allow a local attacker cause DOS through type confusion.

in OpenHarmony v5.0.2 and prior versions allow a local attacker case DOS through missing release of memory.

in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through NULL pointer dereference.

in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through NULL pointer dereference.

in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through NULL pointer dereference.

in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through NULL pointer dereference.

in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through NULL pointer dereference.

in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through improper input.

in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through out-of-bounds write.

in OpenHarmony v5.0.3 and prior versions allow a local attacker cause DOS through buffer overflow.

in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through buffer overflow.

in OpenHarmony v5.0.3 and prior versions allow a local attacker cause DOS through out-of-bounds read.

in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through out-of-bounds read.

in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through buffer overflow.

in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through out-of-bounds read.

in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through out-of-bounds read.

in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through out-of-bounds read.

in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through out-of-bounds read.

in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through out-of-bounds read.

in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through NULL pointer dereference.

in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through out-of-bounds read.

in OpenHarmony v5.0.3 and prior versions allow a local attacker cause apps crash through type confusion.

in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through NULL pointer dereference.

in OpenHarmony v5.0.3 and prior versions allow a local attacker cause apps crash through type confusion.

in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through out-of-bounds read.

in OpenHarmony v5.0.2 and prior versions allow a local attacker cause DOS through out-of-bounds read.

Kernel subsystem within OpenHarmony-v3.1.4 and prior versions in kernel_liteos_a has a kernel stack overflow vulnerability when call SysClockGetres. 4 bytes padding data from kernel stack are copied to user space incorrectly and leaked.

in OpenHarmony v4.0.0 and prior versions allow a local attacker cause DOS through out-of-bounds read.

in OpenHarmony v4.1.0 and prior versions allow a local attacker cause DOS through out-of-bounds write.

in OpenHarmony v4.0.0 and prior versions allow a local attacker cause service crash through NULL pointer dereference.

in OpenHarmony v3.2.4 and prior versions allow a local attacker cause apps crash through get permission.

in OpenHarmony v4.1.0 and prior versions allow a local attacker cause DOS through improper input.

in OpenHarmony v4.0.0 and prior versions allow a local attacker cause service crash through integer overflow.

in OpenHarmony v4.0.0 and prior versions allow a local attacker cause apps crash through type confusion.

in OpenHarmony v3.2.4 and prior versions allow a local attacker cause DOS through stack overflow.

in OpenHarmony v4.0.0 and prior versions allow a local attacker cause apps crash through type confusion.

A vulnerability was found in GNU Binutils 2.44 and classified as problematic. This issue affects the function process_debug_info of the file binutils/dwarf.c of the component DWARF Section Handler. The manipulation leads to memory leak. Attacking locally is a requirement. The identifier of the patch is e51fdff7d2e538c0e5accdd65649ac68e6e0ddd4. It is recommended to apply a patch to fix this issue.

A flaw has been found in LibTIFF 4.7.0. This affects the function _TIFFmallocExt/_TIFFCheckRealloc/TIFFHashSetNew/InitCCITTFax3 of the file tools/tiffcmp.c of the component tiffcmp. Executing manipulation can lead to memory leak. The attack is restricted to local execution. The exploit has been published and may be used. This patch is called ed141286a37f6e5ddafb5069347ff5d587e7a4e0. It is best practice to apply a patch to resolve this issue.

A vulnerability, which was classified as problematic, has been found in HDF5 1.14.6. This issue affects the function H5FL__malloc of the file src/H5FL.c. The manipulation leads to memory leak. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used.