Security Resilience

CVE-2024-10630

Race Condition in Ivanti Application Control ≤ 2023.3

Race Condition
Published
14 January 2025
Modified
11 July 2025
Patch / advisory
View advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0023 12th percentile
Risk Priority 55 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-10630 is a high-severity Race Condition within a Thread (CWE-366) vulnerability in Ivanti Application Control. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique NTDS (T1003.003); ranked at the 12th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-10630 is a race condition vulnerability, classified under CWE-366, affecting Ivanti Application Control Engine in versions prior to 10.14.4.0. This flaw enables a local authenticated attacker to bypass the application's blocking functionality, undermining endpoint security controls designed to restrict unauthorized software execution. The vulnerability carries a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), reflecting high potential impacts on confidentiality, integrity, and availability within the local scope.

A low-privileged local authenticated user can exploit this race condition by timing operations to evade blocking mechanisms, allowing execution of restricted or malicious applications. Successful exploitation grants the attacker high-level access to system resources, potentially leading to unauthorized data access, modification, or disruption without requiring user interaction.

Ivanti has issued a security advisory detailing the vulnerability at https://forums.ivanti.com/s/article/Security-Advisory-Ivanti-Application-Control-Engine-CVE-2024-10630, which recommends upgrading to version 10.14.4.0 or later to mitigate the issue.

EU & UK References

Vulnerability Data

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.

CWE(s)
CWE-366

Related Threats

MITRE ATT&CK Enterprise Techniques

T1003.003 NTDS Credential Access
Adversaries may attempt to access or create a copy of the Active Directory domain database in order to steal credential information, as well as obtain other information about domain members such as devices, users, and access rights.
attack.mitre.org →
T1003.004 LSA Secrets Credential Access
Adversaries with SYSTEM access to a host may attempt to access Local Security Authority (LSA) secrets, which can contain a variety of different credential materials, such as credentials for service accounts.
attack.mitre.org →
T1006 Direct Volume Access Stealth
Adversaries may directly access a volume to bypass file access controls and file system monitoring.
attack.mitre.org →
T1007 System Service Discovery Discovery
Adversaries may try to gather information about registered local system services.
attack.mitre.org →
T1008 Fallback Channels Command And Control
Adversaries may use fallback or alternate communication channels if the primary channel is compromised or inaccessible in order to maintain reliable command and control and to avoid data transfer thresholds.
attack.mitre.org →
T1010 Application Window Discovery Discovery
Adversaries may attempt to get a listing of open application windows.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-11598Same product: Ivanti Application Control
CVE-2024-10251Same product: Ivanti Security Controls
CVE-2026-46181Shared CWE-366
CVE-2026-3904Shared CWE-366
CVE-2026-25687Shared CWE-366
CVE-2025-58143Shared CWE-366
CVE-2023-4127Shared CWE-366
CVE-2023-3218Shared CWE-366
CVE-2026-22819Shared CWE-366
CVE-2026-86247Shared CWE-366

Affected Assets

ivanti
application control
2023.3, 2024.1, 2024.3 · ≤ 2023.3 · ≤ 2023.3
ivanti
security controls
≤ 2024.4.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V15.4.2
  • V15.4.3
  • V17.2.6

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can include concurrency and stress testing that finds race conditions after they have been coded.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented development standards and tools can mandate use of safe concurrency patterns that avoid introducing races.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles include requirements for synchronization primitives and thread-safe design that stop race conditions from being introduced.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 partial match
blocks

Secure SDLC practices directly require synchronization primitives and concurrency analysis that prevent intra-thread race conditions.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.19 Installation of software on operational systems partial match
removes
A.8.25 Secure development life cycle partial match
blocks

A.8.25 mandates secure SDLC practices (secure coding guidelines, security requirements, checkpoints, testing including code scans/penetration tests, and developer training) that reach race conditions in multithreaded code, but leaves a bounded remainder where implementation is incomplete or the specific synchronization flaw slips past the chosen methodology and tests.

A.8.26 Application security requirements partial match
blocks

A.8.26 only requires that race-condition-relevant requirements (e.g. thread safety, synchronization) be identified during requirements gathering; it performs no enforcement, design, or implementation act that stops the CWE-366 condition from being exploitable when present.

A.8.27 Secure system architecture and engineering principles partial match
blocks

Secure architecture principles address concurrent access and resource synchronization.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require proper synchronization primitives to prevent race conditions.

A.8.29 Security testing in development and acceptance partial match
finds

Security testing can detect race conditions through concurrency and stress testing.

References