CVE-2024-23535
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA Path Traversal vulnerability in web component of Ivanti Avalanche before 6.4.3 allows a remote authenticated attacker to execute arbitrary commands as SYSTEM.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA path traversal vulnerability in the web component of Ivanti Avalanche before version 6.4.3 allows a remote authenticated attacker to traverse filesystem paths and execute arbitrary commands with SYSTEM-level privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 6.4.3.528CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Ivanti Avalanche is installedCheck for Ivanti Avalanche installation directories (commonly C:\Program Files\Ivanti\Avalanche or C:\Program Files (x86)\Ivanti\Avalanche) or search for avalanche.exe in the system.Affected if Ivanti Avalanche software is found on the system
-
Determine installed versionLocate the version information - check the Avalanche installation directory for a version file, or right-click on avalanche.exe and select Properties > Details to view File Version. The version format appears as X.X.X.X.Affected if The version number displayed is less than 6.4.3.528
-
Confirm web component is accessibleCheck if the Avalanche web interface is running - typically accessible on port 80/443 or check IIS or the Avalanche web service status.Affected if The web component is exposed or running
-
Verify SYSTEM-level privileges potentialConfirm the Avalanche Windows service runs under the SYSTEM account or an administrator account by opening Services > Ivanti Avalanche Service > Properties > Log On.Affected if The service runs with elevated (SYSTEM or administrator) privileges
The environment is affected if Ivanti Avalanche is installed with a version lower than 6.4.3.528 and the web component is accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.4.3.528
Upgrade Ivanti Avalanche to version 6.4.3 or later to remediate the path traversal vulnerability in the web component.
6.4.3.528 or later
- 1. Obtain Ivanti Avalanche version 6.4.3.528 or later from the official Ivanti download portal or support site
- 2. Create a full backup of the current Avalanche installation including configuration files and database
- 3. Review Ivanti's upgrade documentation for Avalanche 6.4.3
- 4. Apply the upgrade to the Avalanche server following standard Ivanti upgrade procedures
- 5. Verify the upgrade was successful by checking the version number in the Avalanche administrative console
- 6. Validate that the path traversal vulnerability is remediated by confirming the fix is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23535 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-23535 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data