CVE-2024-44104
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 · uneditedAn incorrectly implemented authentication scheme that is subjected to a spoofing attack in the management console of Ivanti Workspace Control before version 2025.2 (10.19.0.0) allows a local authenticated attacker to escalate their privileges.
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 before version 2025.2 (10.19.0.0) contains an incorrectly implemented authentication scheme in its management console that is vulnerable to spoofing, allowing a local authenticated attacker to escalate privileges to higher permission levels.
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.
-
Verify Ivanti Workspace Control is installedCheck for the presence of Ivanti Workspace Control in the system by looking in Program Files or checking Windows Services for 'Ivanti Workspace Control' serviceAffected if The product is not installed or the service does not exist
-
Determine installed versionOpen Windows Registry and navigate to HKLM\SOFTWARE\ivanti\workspacecontrol (or HKLM\SOFTWARE\WOW6432Node\ivanti\workspacecontrol) and read the 'Version' value, or right-click the application executable and view Properties > Details for the File VersionAffected if The version displayed is lower than 10.18.99.0 (or 10.19.0.0 or later indicates patched)
-
Confirm management console is accessibleCheck if the Ivanti Workspace Control management console (typically accessed via the admin UI or web interface) is enabled and accessible on the systemAffected if The management console is enabled and the version is below 10.18.99.0
The system is affected if Ivanti Workspace Control is installed with a version lower than 10.18.99.0 and the management console is accessible to a local authenticated user.
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 to remediate this vulnerability.
2025.2 (10.19.0.0)
- 1. Back up the current Ivanti Workspace Control configuration and database
- 2. Download Ivanti Workspace Control version 2025.2 (10.19.0.0) or later from the official Ivanti download portal
- 3. Stop the Ivanti Workspace Control services on the management console
- 4. Run the installer for version 10.19.0.0
- 5. Follow the on-screen upgrade wizard instructions, preserving existing settings
- 6. After installation, verify the upgrade was successful by checking the version in the management console
- 7. Restart all Ivanti Workspace Control services
- 8. Test that authentication and privilege escalation is properly enforced
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-44104 — 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-44104 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