Cryptospike: Improper Validation of Integrity Check Value
CVE-2023-36650 is a high-severity improper validation of integrity check value vulnerability in Cryptospike from Prolion, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. Affected Cryptospike versions: 3.0.15. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.39% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Cryptospike you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Prolion | Cryptospike | 3.0.15 | Not stated |
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Validation of Integrity Check Value
The product does not validate or incorrectly validates the integrity check values or checksums of a message.
How developers prevent this class of flaw
- The protocol specification describes the algorithm used for calculating the checksum. It is then a matter of implementing the calculation and verifying that the calculated checksum and the received checksum match.
More Improper Validation of Integrity Check Value vulnerabilities (CWE-354)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Technical write-ups (may include proof of concept)
- cvcn.gov.it/cvcn/cve/CVE-2023-36650Exploit, Third Party Advisory
Other vulnerabilities in Cryptospike
- 7.2 High severity
- 9.1 Critical severity
- 8.2 High severity
- 7.5 High severity
- 8.8 High severity
- 9.8 Critical severity
Recent Improper Validation of Integrity Check Value vulnerabilities
- 7.5 High severity
- 8.8 High severity
- 7.5 High severity
- 7.8 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.