VulDB Recent Entries

A vulnerability was found in Qualcomm Snapdragon Auto. It has been declared as problematic. Affected by this vulnerability is an unknown functionality. The manipulation leads to time-of-check time-of-use. This vulnerability is known as CVE-2025-21431. Local access is required to approach this attack. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability was found in Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Industrial IOT and Snapdragon Mobile. It has been classified as critical. Affected is an unknown function of the component TME. The manipulation leads to use of out-of-range pointer offset. This vulnerability is traded as CVE-2024-45557. An attack has to be approached locally. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability was found in Qualcomm Snapdragon CCW, Snapdragon Compute, Snapdragon Wearables and Snapdragon Wired Infrastructure and Networking and classified as problematic. This issue affects some unknown processing of the component TCSR. The manipulation leads to improper access control for register interface. The identification of this vulnerability is CVE-2024-45556. The attack needs to be approached locally. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability has been found in Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile and Snapdragon WBC and classified as critical. This vulnerability affects unknown code of the component EHT Operation Parser. The manipulation leads to buffer over-read. This vulnerability was named CVE-2025-21434. The attack can be initiated remotely. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability, which was classified as critical, was found in Qualcomm Snapdragon Auto. This affects an unknown part of the component IOCTL Handler. The manipulation leads to use after free. This vulnerability is uniquely identified as CVE-2025-21437. Attacking locally is a requirement. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability, which was classified as problematic, has been found in Qualcomm Snapdragon Auto, Snapdragon CCW, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Technology, Snapdragon WBC and Snapdragon Wearables. Affected by this issue is some unknown functionality of the component Gatekeeper. The manipulation leads to weak authentication. This vulnerability is handled as CVE-2024-45551. Local access is required to approach this attack. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability classified as critical was found in Qualcomm Snapdragon Auto. Affected by this vulnerability is an unknown functionality of the component Header Handler. The manipulation leads to integer overflow to buffer overflow. This vulnerability is known as CVE-2025-21442. An attack has to be approached locally. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability classified as critical has been found in Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile and Snapdragon Wearables. Affected is an unknown function of the component RTCP Packet Handler. The manipulation leads to buffer over-read. This vulnerability is traded as CVE-2024-45552. It is possible to launch the attack remotely. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability was found in Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Industrial IOT and Snapdragon Wearables. It has been rated as critical. This issue affects some unknown processing of the component IOCTL Call Handler. The manipulation leads to use after free. The identification of this vulnerability is CVE-2024-45544. It is possible to launch the attack on the local host. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability was found in Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile and Snapdragon Wearables. It has been declared as critical. This vulnerability affects unknown code of the component MSM Channel Handler. The manipulation leads to out-of-bounds write. This vulnerability was named CVE-2024-45543. Attacking locally is a requirement. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability was found in Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile and Snapdragon Wearables. It has been classified as critical. This affects an unknown part of the component IOCTP Map Handler. The manipulation leads to use after free. This vulnerability is uniquely identified as CVE-2024-45540. Local access is required to approach this attack. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability was found in Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile and Snapdragon Wearables and classified as critical. Affected by this issue is some unknown functionality of the component File Descriptor Handler. The manipulation leads to use after free. This vulnerability is handled as CVE-2024-43066. An attack has to be approached locally. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability has been found in Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile and Snapdragon Wearables and classified as critical. Affected by this vulnerability is an unknown functionality of the component EEPROM Handler. The manipulation leads to time-of-check time-of-use. This vulnerability is known as CVE-2024-43067. The attack needs to be approached locally. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability, which was classified as critical, was found in Qualcomm Snapdragon Mobile FastConnect 6900/FastConnect 7800/WCD9380/WSA8830/WSA8835. Affected is an unknown function of the component IOCTL Call Handler. The manipulation leads to incorrect type conversion. This vulnerability is traded as CVE-2024-43058. It is possible to launch the attack on the local host. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability, which was classified as problematic, has been found in Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Technology, Snapdragon WBC and Snapdragon Wearables. This issue affects some unknown processing of the component RKP. The manipulation leads to exposed dangerous routine. The identification of this vulnerability is CVE-2024-43065. Attacking locally is a requirement. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability classified as problematic was found in Qualcomm Snapdragon Auto, Snapdragon CCW, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon MC, Snapdragon MDM, Snapdragon Mobile, Snapdragon Technology, Snapdragon WBC and Snapdragon Wearables. This vulnerability affects unknown code of the component MQ Channel Creation. The manipulation leads to exposure of sensitive system information to an unauthorized control sphere. This vulnerability was named CVE-2024-45549. Local access is required to approach this attack. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability classified as critical has been found in Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon MDM, Snapdragon Mobile, Snapdragon Technology and Snapdragon WBC. This affects an unknown part of the component HLOS. The manipulation leads to insufficient granularity of access control. This vulnerability is uniquely identified as CVE-2024-33058. An attack has to be approached locally. There is no exploit available. It is recommended to 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 MDM, Snapdragon Mobile, Snapdragon Technology, Snapdragon Voice & Music, Snapdragon WBC, Snapdragon Wearables and Snapdragon Wired Infrastructure and Networking. It has been rated as problematic. Affected by this issue is some unknown functionality of the component TZ Secure OS. The manipulation leads to information disclosure. This vulnerability is handled as CVE-2024-43046. The attack needs to be approached locally. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability was found in FCJ Venture Builder appclientefiel 3.0.27. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the file /rest/cliente/ObterPedido/ of the component HTTP GET Request Handler. The manipulation of the argument ORDER_ID leads to improper control of resource identifiers. This vulnerability is known as CVE-2025-3405. The attack can be launched remotely. Furthermore, there is an exploit available. The vendor was contacted early about this disclosure but did not respond in any way.

A vulnerability was found in Vivotek NVR ND8422P, NVR ND9525P and NVR ND9541P 2.4.0.204/3.3.0.104/4.2.0.101. It has been classified as problematic. Affected is an unknown function of the component HTML Form Handler. The manipulation leads to inclusion of sensitive information in source code. This vulnerability is traded as CVE-2025-3403. It is possible to launch the attack remotely. Furthermore, there is an exploit available. The vendor was contacted early about this disclosure but did not respond in any way.