dbcve.org
Workspace ControlApplication · Ivanti

CVE-2024-8012

HIGH · 7.8 CVSS v3.1 Published 2024-09-10
Fix available
A fix is available. Upgrade to 10.18.99.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
An authentication bypass weakness in the message broker service 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 · moderate confidence

An authentication bypass vulnerability in the message broker service of Ivanti Workspace Control allows a local authenticated attacker to bypass proper authentication checks and escalate privileges to higher permission levels within the system.

MitigationUpgrade Ivanti Workspace Control to version 2025.2 (10.19.0.0) or later to remediate the authentication bypass in the message broker service.

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.18.99.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 Programs and Features or use command: wmic product get name,version where name like '%Ivanti Workspace Control%'
    Affected if Installed version is below 10.18.99.0 (or version cannot be determined and the product is present)
  2. Verify message broker service presence
    Open Services console (services.msc) or run: sc query type= service state= all | findstr /i "message broker"
    Affected if A message broker service related to Ivanti Workspace Control exists and is running
  3. Check service configuration and authentication settings
    Inspect service properties in Services console to confirm the service runs under a local system or service account with elevated privileges
    Affected if The message broker service runs with elevated privileges (SYSTEM or service account with admin rights)
  4. Review local user permissions
    Run whoami /all or check Local Users and Groups (lusrmgr.msc) to identify if any local users exist on the system
    Affected if Local authenticated users exist on the machine (required attack vector)
  5. Cross-reference version with vendor release notes
    Check Ivanti Workspace Control version history or release notes to confirm the exact installed build number and compare against 10.18.99.0
    Affected if Version is 10.18.99.0 or lower, or version cannot be verified

A system is affected if Ivanti Workspace Control version is below 10.18.99.0 AND the message broker service is installed and running, allowing a local authenticated user to potentially bypass authentication and escalate privileges.

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.18.99.0 or later
Fixed in 10.18.99.0
Interim mitigation

Upgrade Ivanti Workspace Control to version 2025.2 (10.19.0.0) or later to remediate the authentication bypass in the message broker service.

Recommended fix High confidence

2025.2 (10.19.0.0)

  1. 1. Identify the current version of Ivanti Workspace Control installed in your environment
  2. 2. Obtain the fixed version (2025.2 / 10.19.0.0) from the official Ivanti download portal or through your Ivanti support contract
  3. 3. Review release notes for version 2025.2 to understand changes and ensure compatibility
  4. 4. Test the upgrade in a non-production environment before deploying to production
  5. 5. Apply the upgrade to production systems following standard change management procedures
  6. 6. Verify the upgrade was successful and the vulnerability is resolved

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8012 — 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-2024-8012 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