VulDB Recent Entries

A vulnerability was found in Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon MDM, Snapdragon Mobile, Snapdragon Technology, Snapdragon Voice & Music, Snapdragon WBC and Snapdragon Wired Infrastructure and Networking. It has been classified as problematic. This affects an unknown part of the component COBR Format Handler. The manipulation leads to cryptographic issues. This vulnerability is uniquely identified as CVE-2024-23362. 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 Qualcomm Snapdragon Auto, Snapdragon Mobile and Snapdragon Wearables and classified as critical. Affected by this issue is some unknown functionality of the component OTA. The manipulation leads to buffer over-read. This vulnerability is handled as CVE-2024-23358. The attack may be launched remotely. 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 Connectivity, 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 FM HCI Command Handler. The manipulation leads to buffer overflow. This vulnerability is known as CVE-2024-33052. Attacking locally is a requirement. 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, Snapdragon Mobile and Snapdragon Wearables. Affected is an unknown function of the component MinkSocket Listener Thread Handler. The manipulation leads to use after free. This vulnerability is traded as CVE-2024-23365. Local access is required to approach this attack. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability, which was classified as critical, has been found in Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon MDM, Snapdragon Mobile, Snapdragon WBC and Snapdragon Wearables. This issue affects some unknown processing of the component Tracking Area Update Message Handler. The manipulation leads to buffer over-read. The identification of this vulnerability is CVE-2024-23359. The attack may be initiated remotely. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability classified as critical was found in Qualcomm Snapdragon Auto, Snapdragon CCW, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon MC, Snapdragon Mobile, Snapdragon Technology, Snapdragon WBC, Snapdragon Wearables and Snapdragon Wired Infrastructure and Networking. This vulnerability affects unknown code of the component Beacon Frame Handler. The manipulation leads to buffer over-read. This vulnerability was named CVE-2024-23364. The attack can be initiated remotely. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability classified as problematic has been found in gix-path. This affects the function gix_path::env. The manipulation leads to information disclosure. This vulnerability is uniquely identified as CVE-2024-8371. Access to the local network is required for this attack. Furthermore, there is an exploit available.

A vulnerability was found in Checkmk up to 2.3.0p13. It has been rated as problematic. Affected by this issue is some unknown functionality of the component Robotmk Logs View. The manipulation leads to cross site scripting. This vulnerability is handled as CVE-2024-38858. The attack may be launched remotely. There is no exploit available. It is recommended to apply a patch to fix this issue.

A vulnerability was found in Flaming Forms Plugin up to 1.0.1 on WordPress. It has been declared as problematic. Affected by this vulnerability is an unknown functionality. The manipulation leads to cross site scripting. This vulnerability is known as CVE-2024-7692. The attack can be launched remotely. There is no exploit available.

A vulnerability was found in Flaming Forms Plugin up to 1.0.1 on WordPress. It has been classified as problematic. Affected is an unknown function. The manipulation leads to cross site scripting. This vulnerability is traded as CVE-2024-7691. It is possible to launch the attack remotely. There is no exploit available.

A vulnerability was found in DN Popup Plugin up to 1.2.2 on WordPress and classified as problematic. This issue affects some unknown processing of the component Setting Handler. The manipulation leads to cross-site request forgery. The identification of this vulnerability is CVE-2024-7690. The attack may be initiated remotely. There is no exploit available.

A vulnerability has been found in Ninja Forms Plugin up to 3.8.10 on WordPress and classified as problematic. This vulnerability affects unknown code. The manipulation leads to cross site scripting. This vulnerability was named CVE-2024-7354. 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 problematic, was found in OpenHarmony up to 4.0.1. This affects an unknown part. The manipulation leads to out-of-bounds read. This vulnerability is uniquely identified as CVE-2024-38382. Attacking locally is a requirement. There is no exploit available.

A vulnerability, which was classified as problematic, has been found in Linen. Affected by this issue is some unknown functionality of the component Setting Handler. The manipulation leads to Privilege Escalation. This vulnerability is handled as CVE-2024-45522. Access to the local network is required for this attack. There is no exploit available. It is recommended to apply a patch to fix this issue.

A vulnerability classified as problematic was found in OpenHarmony up to 4.0.1. Affected by this vulnerability is an unknown functionality. The manipulation leads to out-of-bounds read. This vulnerability is known as CVE-2024-39612. An attack has to be approached locally. There is no exploit available.

A vulnerability classified as problematic has been found in OpenHarmony up to 4.1.0. Affected is an unknown function. The manipulation leads to integer overflow. This vulnerability is traded as CVE-2024-28044. The attack needs to be approached locally. There is no exploit available.

A vulnerability was found in OpenHarmony up to 4.1.0. It has been rated as critical. This issue affects some unknown processing. The manipulation leads to use after free. The identification of this vulnerability is CVE-2024-41160. It is possible to launch the attack on the local host. There is no exploit available.

A vulnerability was found in OpenHarmony up to 4.1.0. It has been declared as critical. This vulnerability affects unknown code. The manipulation leads to use after free. This vulnerability was named CVE-2024-41157. Attacking locally is a requirement. There is no exploit available.

A vulnerability was found in OpenHarmony up to 4.1.0. It has been classified as critical. This affects an unknown part of the component Pre-installed Apps. The manipulation leads to out-of-bounds write. This vulnerability is uniquely identified as CVE-2024-39816. Local access is required to approach this attack. There is no exploit available.

A vulnerability was found in OpenHarmony up to 4.1.0 and classified as critical. Affected by this issue is some unknown functionality of the component Pre-installed Apps. The manipulation leads to out-of-bounds write. This vulnerability is handled as CVE-2024-38386. An attack has to be approached locally. There is no exploit available.