CVE Vulnerability Catalog

Active IQ OneCollect version 2.7.3 contains hard-coded credentials that could allow an authenticated attacker with low privileges to perform unauthorized AutoSupport operations.

Active IQ Config Advisor version 6.7.3 contains hard-coded credentials that could allow an authenticated attacker with low privileges to perform unauthorized AutoSupport operations.

Server-Side Request Forgery (SSRF) vulnerability in the RestTemplate.getForEntity function in RestTemplateUtil.java in crmeb_java 1.4. An attacker can remotely manipulate the URL argument in the base64 Qrcode endpoint, leading to unauthorized server requests.

Acronis DeviceLock DLP for Windows prior to build 9.0.15051.93227 is vulnerable to local privilege escalation via DLL hijacking.

Local privilege escalation due to DLL hijacking vulnerability. Affects Acronis DeviceLock DLP (Windows) before build 9.0.15051.93227.

Local privilege escalation due to EXE hijacking vulnerability in Acronis DeviceLock DLP (Windows) before build 9.0.15051.93227.

A vulnerability in Acronis DeviceLock DLP (Windows) before build 9.0.15051.93227 allows local privilege escalation due to excessive permissions assigned to child processes.

Version 3.0.7 of the Securly Chrome Extension uses deprecated SHA-1 hashing for IWF CSAM URL matching (25,020 hashes) and CIPA blocklist matching (12,352 hashes).

Securly Chrome Extension version 3.0.7 downloads config.json over HTTP and compiles server-provided patterns as JavaScript regular expressions via new RegExp() without complexity validation. An on-path attacker can inject patterns causing catastrophic backtracking, resulting in denial of service on all browsing.

Securly Chrome Extension version 3.0.7 uses EVP_BytesToKey with MD5 and a single iteration for AES encryption. MD5 has been broken since 2004 and a single iteration provides no key stretching, weakening the encryption.

Securly Chrome Extension version 3.0.7 dynamically registers content13.min.js as a content script not declared in manifest.json, bypassing Chrome Web Store static security review. It runs on all URLs, immediately hides all page content, creates a full-page overlay, pauses all videos, and only restores content when the service worker confirms the page passes filtering. If Securly's servers are unreachable, pages remain indefinitely hidden.

Version 3.0.7 of the Securly Chrome Extension exposes multiple publicly accessible endpoints that allow unauthenticated access to sensitive data. The exposed information consists of SHA-1 hashes obfuscated with a simple Caesar cipher that can be easily reversed.

Version 3.0.7 of the Securly Chrome Extension contains hardcoded, plaintext AES passphrases in securly.min.js. These keys decrypt crisis alert keyword data and intervention site data.

Securly Chrome Extension version 3.0.7 downloads JSON files containing crisis alert keywords and filtering rules over unencrypted HTTP via the Fetch API. Other endpoints in the same extension correctly fetch IWF and CIPA data over HTTPS, demonstrating an inconsistent TLS implementation.

Concrete CMS below 9.5.3 is vulnerable to PHP Object Injection via unserialize() calls in the Workflow, Form block, and File/Set components that lack the allowed_classes restriction. The Form block and File/Set sinks were addressed in 9.5.2; the Workflow component sinks were addressed in 9.5.3. An unauthenticated attacker may trigger arbitrary PHP object instantiation if a malicious serialized payload has been placed in the database.

In the Linux kernel, the ibmveth driver has an issue with GSO segmentation for packets with small MSS (below 224 bytes). Attempting to send such packets freezes the adapter, stopping all traffic until manual reset.

In the Linux kernel, the ath12k Wi-Fi driver causes firmware crash on WCN7850 when WoW offloads are enabled on both primary and secondary links in multi-link connections. Fixed by enabling WoW only on the primary link.

In the rt9455 power supply driver in the Linux kernel, there is a use-after-free vulnerability in power_supply_changed(). The order of IRQ and power_supply registration is incorrect, leading to use of a freed pointer.

In the Linux kernel, the NFC HCI SHDLC subsystem fails to stop timers and work before freeing context, leading to use-after-free (UAF) and other shutdown races.

In the Linux kernel, a problem was detected in the RDMA hns driver where during a reset triggered by sunrpc, the hns_roce_irq_workq workqueue is flushed but lacks the WQ_MEM_RECLAIM flag, causing a warning and potential memory allocation issues. The issue occurs during QP destruction, leading to memory leaks.