Skip to content

Vendor

prolion vulnerabilities

9 published CVES affecting prolion, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
9
Critical
2
High
5
Medium
2
Low
0
Unscored
0
CISA KEV
0
Atom feed of prolion alerts

Products

Latest prolion CVEs

Newest publication first

  1. HighCVSS 8.2 EPSS 0.98%

    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).

  2. HighCVSS 7.5 EPSS 0.75%

    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.

  3. MediumCVSS 6.5 EPSS 1.2%

    Directory traversal in the log-download REST API endpoint in ProLion CryptoSpike 3.0.15P2 allows remote authenticated attackers to download host server SSH private keys (associated with a Linux root user) by injecting paths inside REST API endpoint parameters.

  4. CriticalCVSS 9.1 EPSS 0.88%

    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...

  5. HighCVSS 8.8 EPSS 0.85%

    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.

  6. CriticalCVSS 9.8 EPSS 0.99%

    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.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.