Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
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 Exploitation for Privilege Escalation (T1068); ranked at the 14th 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
- 🇪🇺 ENISA EUVD: EUVD-2024-33589
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)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V15.4.2V15.4.3V17.2.6
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can include concurrency and stress testing that finds race conditions after they have been coded.
Requiring documented development standards and tools can mandate use of safe concurrency patterns that avoid introducing races.
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.
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.
Security testing can detect race conditions through concurrency and stress testing.
Secure development lifecycle includes concurrency and synchronization practices that reduce race conditions.
Application security requirements can mandate thread-safety and locking controls.
Secure architecture principles address concurrent access and resource synchronization.
Secure coding standards directly require proper synchronization primitives to prevent race conditions.
Change management can introduce or remove synchronization flaws during updates.