CVE-2024-36136
Ivanti Avalanche 6.3.1 … 6.4.2
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2024-36136 is a high-severity Off-by-one Error (CWE-193) vulnerability in Ivanti Avalanche. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 19% 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 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-36136 is an off-by-one error in the WLInfoRailService component of Ivanti Avalanche version 6.3.1. The flaw produces a denial-of-service condition when triggered, reflected in its CVSS 3.1 base score of 7.5 with network attack vector, no authentication or user interaction required, and high availability impact.
A remote unauthenticated attacker can send a crafted request to the affected service over the network, causing it to crash and interrupting availability for legitimate users or dependent management functions. No confidentiality or integrity loss occurs.
The referenced Ivanti security advisory addresses this issue alongside several other CVEs and directs customers to upgrade to a fixed release, specifically Avalanche 6.4.4 or later, as the primary mitigation.
EPSS for the vulnerability rose from a low baseline to a recorded peak of 0.0801 before settling at the current value of 0.0628, indicating measurable post-disclosure exploitation interest that warrants renewed monitoring.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-35894
Vulnerability Data
An off-by-one error in WLInfoRailService in Ivanti Avalanche 6.3.1 allows a remote unauthenticated attacker to crash the service, resulting in a DoS.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.2.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover off-by-one errors in loops, bounds, and calculations before deployment.
Requiring documented development standards and tools can embed bounds-checking and arithmetic-correctness rules that stop off-by-one mistakes at introduction.
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 prevent off-by-one errors via reviews, static analysis, and testing.
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 in development and acceptance can detect off-by-one errors before release.
Secure development life cycle includes requirements and reviews that can catch off-by-one errors.
Application security requirements can specify bounds-checking and input validation to prevent off-by-one errors.
Secure system architecture and engineering principles promote defensive coding practices that reduce off-by-one mistakes.
Secure coding directly addresses off-by-one errors through coding standards and peer review.