dbcve.org
Application ControlApplication · Ivanti

CVE-2024-10630

HIGH · 7.0 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 2023.3 or later.
See remediation →
72/100
Remediation priority · Elevated
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 race condition in Ivanti Application Control Engine before version 10.14.4.0 allows a local authenticated attacker to bypass the application blocking functionality.

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

A race condition vulnerability exists in Ivanti Application Control Engine prior to version 10.14.4.0 that allows a local authenticated attacker to bypass the application's blocking controls. The vulnerability exploits timing windows in the application's control logic, enabling malicious applications to execute despite being blocked by the policy engine.

MitigationUpgrade Ivanti Application Control Engine to version 10.14.4.0 or later to remediate this vulnerability. Since the attacker requires local authenticated access, also review and limit local user privileges where possible.

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
Application ControlApplication
Affected:< 2023.3= 2023.3= 2024.1= 2024.3
Security ControlsApplication
Affected:<= 2024.4.1

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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. Identify Ivanti Application Control installation and version
    Check the installed version of Ivanti Application Control. On Windows, this can be done via Control Panel > Programs and Features, or by querying the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Ivanti Application Control', or using PowerShell: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like '*Ivanti*Application*Control*'} | Select-Object DisplayName, DisplayVersion
    Affected if The installed version matches < 2023.3, = 2023.3, = 2024.1, or = 2024.3
  2. Identify Ivanti Security Controls installation and version
    Check the installed version of Ivanti Security Controls. On Windows, this can be done via Control Panel > Programs and Features, or by querying the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Ivanti Security Controls', or using PowerShell: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like '*Ivanti*Security*Controls*'} | Select-Object DisplayName, DisplayVersion
    Affected if The installed version is 2024.4.1 or lower
  3. Verify Application Control policy engine is active
    Confirm that the Application Control or policy enforcement feature is actually enabled and running. This can typically be verified through the Ivanti console, or by checking the status of the Ivanti Application Control service in Windows Services (service name typically contains 'Application Control' or 'Polyfill'). Also check if any application blocking policies are configured and active.
    Affected if The policy engine and blocking controls are enabled and actively enforcing application restrictions, making the race condition bypass relevant

You are affected if you have Ivanti Application Control version 2023.3, 2024.1, or 2024.3 (or any version prior to 2023.3), or Ivanti Security Controls version 2024.4.1 or lower, and you have the application blocking controls enabled.

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 2023.3 or later
Fixed in 2023.3
Interim mitigation

Upgrade Ivanti Application Control Engine to version 10.14.4.0 or later to remediate this vulnerability. Since the attacker requires local authenticated access, also review and limit local user privileges where possible.

Recommended fix Moderate confidence

Application Control: 10.14.4.0 or later; Security Controls: version newer than 2024.4.1

  1. 1. Identify the exact Ivanti product in use (Application Control or Security Controls) and current installed version
  2. 2. For Application Control: Upgrade to version 10.14.4.0 or later as specified in the official description
  3. 3. For Security Controls: Upgrade to a version newer than 2024.4.1 that includes the 10.14.4.0 fix
  4. 4. After upgrade, verify the application blocking functionality is working correctly
  5. 5. Test that the race condition is no longer exploitable by the local authenticated attacker

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

Fix this in Application Control Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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