# CVE-2024-10630: Race condition in Application Control Engine

> A local authenticated attacker can exploit a race condition to bypass application blocking functionality in Ivanti Application Control Engine.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jan 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-885j-xrf7-wxg5

## What is CVE-2024-10630?

CVE-2024-10630 is a high-severity vulnerability in Ivanti Application Control Engine, published on 14 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-366 (Race Condition within a Thread)

## Which versions are affected by CVE-2024-10630?

It affects 2 products.


Products: Ivanti Application Control, Ivanti Security Controls.

## How do I fix CVE-2024-10630?

No fix has been published for CVE-2024-10630 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-10630 being exploited?

There is no known exploitation of CVE-2024-10630 in the wild and no public exploit code.

## Other vulnerabilities in Ivanti Application Control Engine

- [CVE-2024-11598](https://insights.sbomify.com/CVE-2024-11598/): Privilege escalation in Application Control (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-10630 and fix it if it is affected.

What it is: CVE-2024-10630 is a high-severity vulnerability in Ivanti Application Control Engine, published on 14 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-10630 in the wild and no public exploit code.

Affected product: Ivanti Application Control Engine. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-10630/ (Markdown: https://insights.sbomify.com/CVE-2024-10630/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-10630
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-10630
- OSV: https://osv.dev/vulnerability/CVE-2024-10630

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-10630/
Summaries are generated and may contain mistakes; the official description above is the record.