CVE-2023-36647: A hard-coded cryptographic private key used to sign JWT authentication tokens in ProLion CryptoSpike 3.0.15P2

This week

HIGH 7.5REMOTEDOWNGRADE

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

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.

Why this priority

High 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 score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.8% (top 45%)
CISA exploited list	No
Weakness	CWE-798
Published	2023-12-12
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: prolion

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

Am I affected?

Timeline

2023-12-12 01:15 UTCPublished CVE record published
2026-06-17 06:06 UTCUpdated Record last modified

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-36647?

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

Is CVE-2023-36647 being exploited?

CVE-2023-36647 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-36647 affect?

CVE-2023-36647 affects cryptospike. Severity is high (CVSS 7.5). 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.

How urgent is CVE-2023-36647?

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

Related CVEs

CVE-2023-36655 CRITICAL 9.8 DOWNGRADE The login REST API in ProLion CryptoSpike 3.0.15P2 (when LDAP or Active Directory is used as the users store)
CVE-2023-36654 MEDIUM 6.5 DOWNGRADE Directory traversal in the log-download REST API endpoint in ProLion CryptoSpike 3.0.15P2 allows remote authen
CVE-2023-36652 MEDIUM 4.3 DOWNGRADE A SQL Injection in the users searching REST API endpoint in ProLion CryptoSpike 3.0.15P2 allows remote authent
CVE-2023-36651 HIGH 7.2 DOWNGRADE Hidden and hard-coded credentials in ProLion CryptoSpike 3.0.15P2 allow remote attackers to login to web manag
CVE-2023-36650 HIGH 7.2 DOWNGRADE A missing integrity check in the update system in ProLion CryptoSpike 3.0.15P2 allows attackers to execute OS

References

← Back to latest CVEs