Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2023-36649: Insertion of sensitive information in the centralized (Grafana) logging system in ProLion CryptoSpike 3.0.15P2

57
This week
CRITICAL 9.1REMOTEDOWNGRADE

CVE-2023-36649 is a critical-severity flaw (CVSS 9.1) affecting cryptospike. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • Critical severity
  • Public exploit reference
  • Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score9.1 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.9% (top 41%)
CISA exploited listNo
WeaknessCWE-532
Published2023-12-12
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: prolion

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

prolion cryptospike DOWNGRADE
Affected: 3.0.15 p2
Fixed in: no fixed release known
Safe to downgrade to: a release before 3.0.15
1. Check installed version
apt-cache policy cryptospike || rpm -q cryptospike || cryptospike --version
2. No fixed release: DOWNGRADE to a release before 3.0.15 (Debian / Ubuntu)
apt-cache madison cryptospike sudo apt install cryptospike=<VERSION_BEFORE_3.0.15> sudo apt-mark hold cryptospike
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list cryptospike sudo dnf downgrade cryptospike-<VERSION_BEFORE_3.0.15> sudo dnf versionlock add cryptospike
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2023-36649?

cryptospike: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2023-36649 being exploited?

CVE-2023-36649 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2023-36649 affect?

CVE-2023-36649 affects cryptospike. Severity is critical (CVSS 9.1). 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 Grana

How urgent is CVE-2023-36649?

Priority 57/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Grafana vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.