CVE-2024-10630

CVE-2024-10630 is a high-severity vulnerability in Ivanti Application Control with a CVSS 3.x base score of 7.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-366.

Key facts

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.

Frequently asked questions

What is CVE-2024-10630?
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.
How severe is CVE-2024-10630?
CVE-2024-10630 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2024-10630 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (13th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-10630?
CVE-2024-10630 primarily affects Ivanti Application Control. In total, 9 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2024-10630?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2024-10630 have an EU (EUVD) identifier?
Yes. CVE-2024-10630 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-33589.
When was CVE-2024-10630 published?
CVE-2024-10630 was published on 2025-01-14 and last updated on 2026-06-17.

References

Affected products (9)

More vulnerabilities in Ivanti Application Control

All CVEs affecting Ivanti Application Control →

Other CWE-366 vulnerabilities

Browse all CWE-366 vulnerabilities →