Cyber Resilience

CVE-2024-36136

Ivanti Avalanche 6.3.1 … 6.4.2

Published
14 August 2024
Modified
15 August 2024
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.022 81th percentile
Risk Priority 65 floored blend · peak EPSS

Summary

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

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

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-27975Same product: Ivanti Avalanche
CVE-2023-38036Same product: Ivanti Avalanche
CVE-2024-29204Same product: Ivanti Avalanche
CVE-2024-24996Same product: Ivanti Avalanche
CVE-2024-23527Same product: Ivanti Avalanche
CVE-2024-50331Same product: Ivanti Avalanche
CVE-2024-23533Same product: Ivanti Avalanche
CVE-2024-23529Same product: Ivanti Avalanche
CVE-2024-23528Same product: Ivanti Avalanche
CVE-2024-23526Same product: Ivanti Avalanche

Affected Assets

ivanti
avalanche
6.3.1, 6.3.1.1507, 6.3.2, 6.3.2.3490, 6.3.3

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)
  • 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.

PR.PS-06 mostly match
prevents

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.

finds

Security testing in development and acceptance can detect off-by-one errors before release.

prevents

Secure development life cycle includes requirements and reviews that can catch off-by-one errors.

prevents

Application security requirements can specify bounds-checking and input validation to prevent off-by-one errors.

prevents

Secure system architecture and engineering principles promote defensive coding practices that reduce off-by-one mistakes.

prevents

Secure coding directly addresses off-by-one errors through coding standards and peer review.

References