MAL-2022-1383 Malicious code in azure-storage-queue (npm)

--- -= Per source details. Do not edit below this line.=- Source: ghsa-malware 817015f4821a3efffc41e7fe04ce95d36839db3aa6b53ce082b70b90c828d865 Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be...

Malware in azure-storage-queue

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outsid...

Malicious code in azure-storage-queue (npm)

--- -= Per source details. Do not edit below this line.=- Source: ghsa-malware 817015f4821a3efffc41e7fe04ce95d36839db3aa6b53ce082b70b90c828d865 Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be...

Malware in storage-queue

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outsid...

MAL-2022-6315 Malicious code in storage-queue (npm)

--- -= Per source details. Do not edit below this line.=- Source: ghsa-malware f293d5b58cea192a649d42d38b37dc26c6dea91a7825405a5359920228abdbf4 Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be...

Malicious code in storage-queue (npm)

--- -= Per source details. Do not edit below this line.=- Source: ghsa-malware f293d5b58cea192a649d42d38b37dc26c6dea91a7825405a5359920228abdbf4 Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be...

amethyst-console (0.1.0), amethyst-imgui (>=0.5.0, <=0.6.0) +50 more potentially affected by unknown CVE via crossbeam-queue (>=0.1.2, <=0.2.0)

crossbeam-queue CARGO version =0.1.2, =0.5.0, =0.1.0, =0.7.0, =0.8.0, =0.7.0, =0.6.0, =0.8.0, =0.7.0, =0.9.0, =0.6.0, =0.6.0, =0.0.1, =0.0.1, =0.2.0, =0.15.3 and more Source cves: unknown CVE Source advisory: OSV:GHSA-6888-WF7J-34JQ...

amethyst-console (0.1.0), amethyst-imgui (>=0.5.0, <=0.6.0) +50 more potentially affected by unknown CVE via crossbeam-queue (>=0.1.2, <=0.2.0)

crossbeam-queue CARGO version =0.1.2, =0.5.0, =0.1.0, =0.7.0, =0.8.0, =0.7.0, =0.6.0, =0.8.0, =0.7.0, =0.9.0, =0.6.0, =0.6.0, =0.0.1, =0.0.1, =0.2.0, =0.15.3 and more Source cves: unknown CVE Source advisory: GHSA-6888-WF7J-34JQ...

CVE-2021-35095

Improper serialization of message queue client registration can lead to race condition allowing multiple gunyah message clients to register with same label in Snapdragon Connectivity, Snapdragon Mobile...

CVE-2021-35092

Processing DCB/AVB algorithm with an invalid queue index from IOCTL request could lead to arbitrary address modification in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music...

Design/Logic Flaw

Processing DCB/AVB algorithm with an invalid queue index from IOCTL request could lead to arbitrary address modification in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music...

Race condition

Improper serialization of message queue client registration can lead to race condition allowing multiple gunyah message clients to register with same label in Snapdragon Connectivity, Snapdragon Mobile...

CVE-2021-35095

CVE-2021-35095 is a Qualcomm/Qualcomm-derived issue affecting Snapdragon components (Snapdragon Connectivity and Snapdragon Mobile) where improper serialization of message queue client registrations can cause a race condition, allowing multiple gunyah message clients to register with the same lab...

CVE-2021-35095

Improper serialization of message queue client registration can lead to race condition allowing multiple gunyah message clients to register with same label in Snapdragon Connectivity, Snapdragon Mobile...

CVE-2021-35095: Deserialization of Untrusted Data

Improper serialization of message queue client registration can lead to race condition allowing multiple gunyah message clients to register with same label in Snapdragon Connectivity, Snapdragon Mobile...

PT-2022-10415 · Qualcomm · Snapdragon Mobile +1

Name of the Vulnerable Software and Affected Versions: Snapdragon Connectivity, Snapdragon Mobile affected versions not specified Description: The issue is related to improper serialization of message queue client registration, which can cause a race condition. This condition allows multiple guny...

ClamAV Buffer Overflow Code Execution

The vulnerability of the ClamAV antivirus software is related to buffer overflow attacks. Exploiting this vulnerability allows a remote attacker to execute arbitrary code by sending specially crafted data...

PT-2022-10412 · Qualcomm · Snapdragon

Name of the Vulnerable Software and Affected Versions: Qualcomm Snapdragon affected versions not specified Description: The issue arises from the processing of DCB/AVB algorithm with an invalid queue index from an IOCTL request, potentially leading to arbitrary address modification. This affects...

Flower Denial of Service Vulnerability

Flower is a Web-based, real-time monitoring and management of Celery distributed task queues. A denial of service vulnerability exists in the May 2, 2022 version of Flower and prior versions, which stems from being vulnerable to OAuth authentication bypass. An attacker can use this vulnerability ...

PT-2025-8312

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A vulnerability in the Linux kernel has been resolved. The issue occurred when the modparam efx separate tx channels=1 was used, causing some channels to only have RX queues and others...