Show filters
545 Total Results
Displaying 111-120 of 545
Sort by:
Attacker Value
Unknown

CVE-2023-36652

Disclosure Date: December 12, 2023 (last updated December 14, 2023)
A SQL Injection in the users searching REST API endpoint in ProLion CryptoSpike 3.0.15P2 allows remote authenticated attackers to read database data via SQL commands injected in the search parameter.
Attacker Value
Unknown

CVE-2023-36651

Disclosure Date: December 12, 2023 (last updated December 14, 2023)
Hidden and hard-coded credentials in ProLion CryptoSpike 3.0.15P2 allow remote attackers to login to web management as super-admin and consume the most privileged REST API endpoints via these credentials.
Attacker Value
Unknown

CVE-2023-36650

Disclosure Date: December 12, 2023 (last updated December 14, 2023)
A missing integrity check in the update system in ProLion CryptoSpike 3.0.15P2 allows attackers to execute OS commands as the root Linux user on the host system via forged update packages.
Attacker Value
Unknown

CVE-2023-36649

Disclosure Date: December 12, 2023 (last updated December 15, 2023)
Insertion of sensitive information in the centralized (Grafana) logging system in ProLion CryptoSpike 3.0.15P2 allows remote attackers to impersonate other users in web management and the REST API by reading JWT tokens from logs (as a Granafa authenticated user) or from the Loki REST API without authentication.
Attacker Value
Unknown

CVE-2023-36648

Disclosure Date: December 12, 2023 (last updated December 14, 2023)
Missing authentication in the internal data streaming system in ProLion CryptoSpike 3.0.15P2 allows remote unauthenticated users to read potentially sensitive information and deny service to users by directly reading and writing data in Apache Kafka (as consumer and producer).
Attacker Value
Unknown

CVE-2023-36647

Disclosure Date: December 12, 2023 (last updated December 14, 2023)
A hard-coded cryptographic private key used to sign JWT authentication tokens in ProLion CryptoSpike 3.0.15P2 allows remote attackers to impersonate arbitrary users and roles in web management and REST API endpoints via crafted JWT tokens.
Attacker Value
Unknown

CVE-2023-36646

Disclosure Date: December 12, 2023 (last updated December 14, 2023)
Incorrect user role checking in multiple REST API endpoints in ProLion CryptoSpike 3.0.15P2 allows a remote attacker with low privileges to execute privileged functions and achieve privilege escalation via REST API endpoint invocation.
Attacker Value
Unknown

CVE-2023-36655

Disclosure Date: December 06, 2023 (last updated December 13, 2023)
The login REST API in ProLion CryptoSpike 3.0.15P2 (when LDAP or Active Directory is used as the users store) allows a remote blocked user to login and obtain an authentication token by specifying a username with different uppercase/lowercase character combination.
Attacker Value
Unknown

CVE-2023-48698

Disclosure Date: December 05, 2023 (last updated December 12, 2023)
Azure RTOS USBX is a USB host, device, and on-the-go (OTG) embedded stack, that is fully integrated with Azure RTOS ThreadX. An attacker can cause remote code execution due to expired pointer dereference vulnerabilities in Azure RTOS USBX. The affected components include functions/processes in host stack and host classes, related to device linked classes, GSER and HID in RTOS v6.2.1 and below. The fixes have been included in USBX release 6.3.0. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Attacker Value
Unknown

CVE-2023-48697

Disclosure Date: December 05, 2023 (last updated December 09, 2023)
Azure RTOS USBX is a USB host, device, and on-the-go (OTG) embedded stack, that is fully integrated with Azure RTOS ThreadX. An attacker can cause remote code execution due to memory buffer and pointer vulnerabilities in Azure RTOS USBX. The affected components include functions/processes in pictbridge and host class, related to PIMA, storage, CDC ACM, ECM, audio, hub in RTOS v6.2.1 and below. The fixes have been included in USBX release 6.3.0. Users are advised to upgrade. There are no known workarounds for this vulnerability.