Workspace Control: Use of Hard-coded Cryptographic Key
CVE-2025-22463 is a high-severity use of hard-coded cryptographic key vulnerability in Workspace Control from Ivanti, with a CVSS 3.1 base score of 7.3 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.36% 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 Workspace Control you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on forums.ivanti.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Ivanti | Workspace Control | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- 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
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L. Scored by CNA.
Official description
A hardcoded key in Ivanti Workspace Control before version 10.19.10.0 allows a local authenticated attacker to decrypt the stored environment password.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Hard-coded Cryptographic Key
The product uses a hard-coded, unchangeable cryptographic key.
How developers prevent this class of flaw
- Prevention schemes mirror that of hard-coded password storage.
More Use of Hard-coded Cryptographic Key vulnerabilities (CWE-321)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Workspace Control
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Recent Use of Hard-coded Cryptographic Key vulnerabilities
- 7.7 High severity
- 8.1 High severity
- 9.8 Critical severity
- 9.0 Critical severity
- 8.3 High severity
- 8.8 High severity
Spotted an error? Tell us.