Vuldb Updates

A vulnerability identified as critical has been detected in Qualcomm Snapdragon Compute, Snapdragon Industrial IOT, Snapdragon Mobile and Snapdragon Wearables. Affected is an unknown function. Performing a manipulation results in buffer overflow. This vulnerability is cataloged as CVE-2025-47394. The attack must be initiated from a local position. There is no exploit available. You should upgrade the affected component.

A vulnerability was found in Qualcomm Snapdragon Compute, Snapdragon Industrial IOT, Snapdragon Mobile and Snapdragon Wearables and classified as critical. This affects an unknown function of the component DSP. The manipulation results in buffer overflow. This vulnerability was named CVE-2025-47388. The attack needs to be approached locally. There is no available exploit. It is suggested to upgrade the affected component.

A vulnerability was found in Qualcomm Snapdragon CCW WCN7861. It has been classified as critical. This impacts an unknown function of the component WLAN Management Frame Handler. This manipulation causes buffer over-read. The identification of this vulnerability is CVE-2025-47395. The attack needs to be done within the local network. There is no exploit available. Upgrading the affected component is recommended.

A vulnerability categorized as problematic has been discovered in Qualcomm Snapdragon Auto, Snapdragon CCW, Snapdragon Compute and Snapdragon Industrial IOT. Affected is an unknown function of the component HLOS. The manipulation results in exposure of sensitive system information to an unauthorized control sphere. This vulnerability was named CVE-2025-47378. The attack needs to be approached locally. There is no available exploit. It is advisable to upgrade the affected component.

A vulnerability, which was classified as critical, has been found in Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Industrial IOT, Snapdragon Mobile and Snapdragon Wearables. The affected element is an unknown function of the component Trusted Execution Environment. This manipulation causes improper access control for register interface. This vulnerability is registered as CVE-2025-47385. The attack needs to be launched locally. No exploit is available. It is advisable to upgrade the affected component.

A vulnerability, which was classified as critical, was found in Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile and Snapdragon WBC. The affected element is an unknown function of the component Trusted Application. Executing a manipulation can lead to out-of-bounds write. This vulnerability is handled as CVE-2025-47346. It is possible to launch the attack on the local host. There is not any exploit available. You should upgrade the affected component.

A vulnerability was found in Qualcomm Snapdragon Auto, Snapdragon CCW, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon WBC and Snapdragon Wearables. It has been classified as problematic. This affects an unknown function of the component HLOS. This manipulation causes exposed dangerous routine. This vulnerability is tracked as CVE-2025-47366. The attack is restricted to local execution. No exploit exists. Upgrading the affected component is recommended.

A vulnerability marked as problematic has been reported in smallvec Crate up to 0.6.12 on Rust. This impacts an unknown function of the component Reference Type Handler. This manipulation causes uninitialized pointer. The identification of this vulnerability is CVE-2018-25023. The attack needs to be done within the local network. There is no exploit available. It is suggested to upgrade the affected component.

A vulnerability, which was classified as problematic, has been found in Marked up to 4.0.9. This vulnerability affects unknown code of the component Regular Expression Handler. The manipulation leads to resource consumption. This vulnerability is uniquely identified as CVE-2022-21681. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.

A vulnerability has been found in log4js-node and classified as critical. This vulnerability affects unknown code of the component Log File. Performing a manipulation results in incorrect default permissions. This vulnerability is identified as CVE-2022-21704. The attack is only possible with local access. There is not any exploit available. The affected component should be upgraded.

A vulnerability has been found in Mailer Plugin up to 391.ve4a_38c1b_cf4b_ on Jenkins and classified as critical. Affected by this issue is some unknown functionality of the component DNS Handler. The manipulation leads to missing authorization. This vulnerability is referenced as CVE-2022-20614. The attack needs to be initiated within the local network. No exploit is available.

A vulnerability described as critical has been identified in Smarty up to 3.1.42/4.0.2. Affected by this vulnerability is an unknown functionality of the component Template Handler. Such manipulation leads to code injection. This vulnerability is uniquely identified as CVE-2021-21408. The attack can be launched remotely. No exploit exists. Upgrading the affected component is recommended.

A vulnerability was found in XBlock Drag and Drop up to 2.x. It has been classified as problematic. Affected is an unknown function of the component Image Handler. The manipulation leads to cross site scripting. This vulnerability is traded as CVE-2022-46147. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended.

A vulnerability categorized as problematic has been discovered in Patchelf 0.9. This affects the function modifyRPath of the file src/patchelf.cc. Such manipulation leads to out-of-bounds read. This vulnerability is referenced as CVE-2022-44940. The attack needs to be initiated within the local network. No exploit is available. It is best practice to apply a patch to resolve this issue.

A vulnerability classified as critical has been found in Smarty up to 3.1.41/4.0.1. Affected by this issue is some unknown functionality of the component Template Handler. Performing a manipulation results in code injection. This vulnerability was named CVE-2021-29454. The attack may be initiated remotely. There is no available exploit. It is recommended to upgrade the affected component.

A vulnerability identified as critical has been detected in diplib 3.0.0. Affected by this issue is some unknown functionality. The manipulation leads to double free. This vulnerability is referenced as CVE-2021-39432. The attack needs to be initiated within the local network. No exploit is available. Applying a patch is the recommended action to fix this issue.

A vulnerability was found in d8s-timer 0.1.0 on Python and classified as critical. Impacted is an unknown function. The manipulation results in backdoor. This vulnerability is reported as CVE-2022-43304. The attacker must have access to the local network to execute the attack. No exploit exists.

A vulnerability was found in d8s-timer 0.1.0 on Python. It has been declared as critical. The impacted element is an unknown function. Such manipulation leads to backdoor. This vulnerability is traded as CVE-2022-43306. Access to the local network is required for this attack to succeed. There is no exploit available.

A vulnerability was found in VMware Workspace one UEM Console. It has been declared as critical. The affected element is an unknown function. Executing a manipulation can lead to server-side request forgery. This vulnerability is handled as CVE-2021-22054. The attack can only be done within the local network. There is not any exploit available. It is recommended to upgrade the affected component.

A vulnerability, which was classified as problematic, was found in WasmEdge up to 0.16.0-alpha.2. This affects the function checkAccessBound of the file WasmEdge/include/runtime/instance/memory.h. Such manipulation leads to integer overflow. This vulnerability is referenced as CVE-2025-69261. It is possible to launch the attack remotely. No exploit is available. You should upgrade the affected component.