| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Eclipse Kura downloads deployment packages (DPs) from a remote URL without any limit on the size of the data it receives. A malicious or compromised HTTP(S) server, or an attacker able to tamper with a plain-HTTP download, can stream an arbitrarily large (or endless) response. Kura writes the response to local storage until the filesystem is full. On gateways the temporary directory is often a RAM-backed tmpfs, so this can also exhaust memory. The result is denial of service of the device: failed configuration persistence, failed logging and possible crashes of the framework or other services.
The same missing size limit is present in the REST upload endpoint `POST /deploy/v2/_upload`, which copies the request body to the temporary directory with no limit.
Workarounds: only install DPs from trusted HTTPS sources, restrict who can install packages (Web UI `kura.packages.admin` permission, REST `kura.permission.rest.deploy`, cloud DEPLOY-V2 access). |
| In the Wi-Fi NPU FW, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local denial of service with user execution privileges needed. User interaction is not needed for exploitation. |
| Multiple injection issues in resource metadata fields in GBIF Integrated Publishing Toolkit versions before 3.3.5 allows authenticated remote attackers to execute code in another user's session after user interaction via stored cross-site scripting |
| Insufficient length validation in the GNSS firmware loader may lead to corruption of kernel memory. |
| Memory corruption in GPU driver due to improper validation of VMID reservation. |
| Out-of-bounds memory access in a device driver due to improper resource state tracking. |
| In the Samsung GPU driver, improper reference count handling during command submission can lead to memory corruption. |
| In the Samsung Exynos GPU driver, improper synchronization during buffer object creation and closing can lead to memory corruption |
| In the Exynos NPU driver, improper validation of user input in the ioctl handler can lead to an out-of-bounds write, which causes a denial of service |
| Insufficient validation of length fields in the GNSS firmware loader can result in kernel‑memory corruption. |
| Integer overflow in NPU driver parameter processing due to insufficient bounds checking. |
| Incorrect authorization in Samsung framework services due to missing permission checks |
| A double free vulnerability in NPU driver due to improper pointer management (941) |
| In the Samsung Exynos ENN NeuralNetworks HAL, improper input validation during request processing can cause memory corruption and lead to a denial of service condition. |
| In the Samsung Exynos H-Arx DRM plugin, improper input validation during buffer operations can cause memory corruption, potentially leading to denial of service or privilege escalation. |
| In the Samsung Exynos NPU driver, improper validation of user input in the ioctl handler can lead to an out-of-bounds write, which causes a denial of service. |
| In the Samsung Exynos NPU kernel driver, an integer overflow allows an unprivileged application to trigger memory corruption. |
| Insufficient input validation in the PowerSYSTEM Center report designer allows an authenticated user to execute unauthorized SQL commands. |
| Incorrect authorization in PowerSYSTEM Center allows a low-privileged, authenticated user to access resources normally limited to administrators. |
| Improper permission handling during buffer operations allows untrusted applications to create memory mappings with inappropriate permissions |
