CVE-2024-44105
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 · uneditedCleartext transmission of sensitive information in the management console of Ivanti Workspace Control before version 2025.2 (10.19.0.0) allows a local authenticated attacker to obtain OS 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 · moderate confidenceIvanti Workspace Control management console transmits OS credentials in cleartext, allowing a locally authenticated attacker to intercept sensitive authentication data. The vulnerability exists in the communication channel between the console and backend systems before version 2025.2 (10.19.0.0).
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.18.99.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.
-
Identify installed Ivanti Workspace Control versionLocate the Ivanti Workspace Control installation directory or check the program's version information through Windows Add/Remove Programs, the application itself, or relevant registry keys under HKLM\Software\Ivanti or similar installation paths.Affected if The installed version number is lower than 10.18.99.0 (for example, 10.18.x.x or earlier).
-
Confirm management console is accessibleVerify that the Ivanti Workspace Control management console component is installed and accessible to users. This is typically accessed through the application GUI or administrative interfaces.Affected if The management console feature is enabled and available in the environment.
-
Verify cleartext credential transmission is occurringInspect network traffic or communication logs between the management console and backend systems using a network sniffer or logging mechanism. Look for unencrypted credential data being transmitted.Affected if OS credentials are being transmitted in cleartext (readable plaintext) rather than being encrypted during console-to-backend communication.
A user is affected if Ivanti Workspace Control version is below 10.18.99.0 AND the management console feature is enabled and transmitting credentials without encryption.
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.18.99.0
Upgrade Ivanti Workspace Control to version 2025.2 (10.19.0.0) or later which implements encrypted transmission of credentials. If immediate upgrade is not feasible, restrict local access to trusted administrators and monitor for credential harvesting activity.
2025.2 (10.19.0.0)
- Backup the current Ivanti Workspace Control configuration and database
- Download Ivanti Workspace Control version 2025.2 (10.19.0.0) or later from the official Ivanti download portal
- Review Ivanti upgrade documentation for version 2025.2
- Execute the upgrade following standard Ivanti upgrade procedures
- After upgrade, verify the management console is accessible and functioning correctly
- Validate that sensitive credentials are now transmitted using encryption rather than cleartext
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-44105 — 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-2024-44105 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