CVE-2025-5353
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 · uneditedA hardcoded key in Ivanti Workspace Control before version 10.19.10.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 confidenceIvanti Workspace Control versions before 10.19.10.0 contain a hardcoded cryptographic key used to encrypt stored SQL database credentials. A local authenticated attacker with access to the system can recover this key and decrypt the stored SQL credentials, potentially gaining unauthorized access to backend databases.
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< 10.19.10.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Ivanti Workspace Control installationLocate the Ivanti Workspace Control installation directory or check registry for installed software, and identify the installed version numberAffected if The software is installed and the version is below 10.19.10.0
-
Check SQL database configurationExamine the application configuration or database connection settings to determine if SQL database credentials are stored/configuredAffected if SQL database credentials are configured and stored by the application
-
Locate encrypted credential storageSearch configuration files, registry keys, or data stores where Ivanti Workspace Control stores encrypted SQL credentialsAffected if Encrypted SQL credentials exist in the environment
-
Identify hardcoded cryptographic keyInspect configuration files, XML files, or embedded resources within the Ivanti Workspace Control installation for a hardcoded cryptographic key used for encryptionAffected if A hardcoded cryptographic key is present in configuration files or application binaries
The environment is affected if Ivanti Workspace Control version is below 10.19.10.0 AND SQL database credentials are stored using the application's encryption mechanism with a hardcoded key.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.19.10.0
Upgrade Ivanti Workspace Control to version 10.19.10.0 or later to replace the hardcoded key with proper key management. After upgrading, rotate all stored SQL credentials as a precautionary measure.
10.19.10.0
- Download Ivanti Workspace Control version 10.19.10.0 or later from the official Ivanti download portal
- Verify the integrity of the downloaded package using checksums provided by Ivanti
- Back up the current Workspace Control configuration and database
- Install the upgrade following the standard Ivanti upgrade procedure
- After upgrade, verify that the hardcoded key vulnerability is remediated by confirming SQL credentials are now encrypted with a proper key management solution
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5353 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-5353 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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