Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2024-50321 is a high-severity Infinite Loop (CWE-835) vulnerability in Ivanti Avalanche. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked in the top 37% of CVEs by exploit likelihood; 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 SI-2 (Flaw Remediation) — 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-50321 is an infinite loop vulnerability, tracked as CWE-835, that affects Ivanti Avalanche versions prior to 6.4.6. The flaw carries a CVSS 3.1 score of 7.5 and permits remote denial of service with no authentication or user interaction required.
A remote unauthenticated attacker can send crafted network requests to trigger the loop, resulting in high availability impact while leaving confidentiality and integrity unaffected.
The official Ivanti security advisory for the Q4 2024 release, which covers this CVE along with additional issues, directs administrators to upgrade to version 6.4.6 or later to resolve the exposure.
The associated EPSS score remains flat at 0.0783 with no material increase observed after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-44817
Vulnerability Data
An infinite loop in Ivanti Avalanche before 6.4.6 allows a remote unauthenticated attacker to cause a denial of service.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover unreachable loop exit conditions through static analysis, fuzzing, or execution tracing.
Flaw remediation processes identify and correct infinite-loop defects reported from testing or operations.
Requiring documented development processes and secure coding standards reduces introduction of loops whose termination conditions are unreachable.
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.
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 uncover infinite-loop conditions before release.
Secure development life cycle mandates practices that can detect and prevent infinite-loop defects.
Application security requirements can specify loop-termination rules, indirectly reducing the weakness.
Secure coding standards directly address loop termination and prevent infinite loops.
Secure architecture principles encourage designs that avoid unreachable exit conditions.
Change management can require review of loop logic when code is modified.