dbcve.org
Workspace ControlApplication · Ivanti

CVE-2025-22455

HIGH · 7.8 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 10.19.10.0 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A hardcoded key in Ivanti Workspace Control before version 10.19.0.0 allows a local authenticated attacker to decrypt stored SQL credentials.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Ivanti Workspace Control before version 10.19.0.0 contains a hardcoded cryptographic key embedded in the application code. This key is used to protect stored SQL database credentials. A local authenticated attacker with access to the system can extract this hardcoded key and use it to decrypt the encrypted SQL credentials stored in the application, potentially gaining unauthorized access to backend databases.

MitigationUpgrade Ivanti Workspace Control to version 10.19.0.0 or later, which replaces the hardcoded key with proper key management. After upgrading, rotate all stored SQL credentials as a precautionary measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Workspace ControlApplication
Affected:< 10.19.10.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Ivanti Workspace Control version
    Open the Ivanti Workspace Control admin console, or check the program version via Windows Control Panel > Programs and Features, or run: powershell "Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Ivanti*Workspace*Control*'} | Select-Object DisplayName, DisplayVersion"
    Affected if The installed version is below 10.19.10.0
  2. Verify SQL database credentials are stored in the application
    Inspect the Ivanti Workspace Control configuration database or configuration files for stored SQL connection strings or encrypted database credentials. Check the application data directory for database connection configuration files.
    Affected if SQL database credentials are stored or configured within the Ivanti Workspace Control application
  3. Confirm credential encryption is enabled
    Review the Ivanti Workspace Control security or database configuration settings in the admin console. Look for settings related to 'encrypted credentials', 'secure connection strings', or 'SQL authentication' with encryption enabled.
    Affected if Credential encryption is turned on in the application settings, meaning the hardcoded key is in use to protect stored SQL passwords
  4. Locate the application binary files containing the hardcoded key
    Examine the Ivanti Workspace Control installation directory (typically under C:\Program Files\Ivanti\Workspace Control) for executable and DLL files. Use a hex editor or strings utility to search for cryptographic key patterns or known key indicators in the application binaries, if you have access to the specific key value from vulnerability disclosure.
    Affected if The application binaries contain a hardcoded cryptographic key used for credential encryption

You are affected if Ivanti Workspace Control is installed at a version below 10.19.10.0 and SQL database credentials are stored with encryption enabled, which would use the hardcoded key for protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.19.10.0 or later
Fixed in 10.19.10.0
Interim mitigation

Upgrade Ivanti Workspace Control to version 10.19.0.0 or later, which replaces the hardcoded key with proper key management. After upgrading, rotate all stored SQL credentials as a precautionary measure.

Recommended fix High confidence

Ivanti Workspace Control 10.19.10.0 or later

  1. 1. Identify the current installed version of Ivanti Workspace Control by checking the software or using system inventory tools
  2. 2. Download Ivanti Workspace Control version 10.19.10.0 or later from the official Ivanti download portal or support site
  3. 3. Before upgrading, back up the current configuration and any stored credential databases
  4. 4. Apply the upgrade following Ivanti's standard upgrade procedure for Workspace Control
  5. 5. After upgrade, verify that the hardcoded cryptographic key has been removed from the configuration
  6. 6. Reconfigure SQL credentials using the new secure credential storage mechanism
  7. 7. Test that Workspace Control functions correctly with the new credential storage
Caveat Minor: May require re-entry of SQL credentials after upgrade due to new credential storage mechanism

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Workspace Control Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22455 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-22455 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data