CVE-2024-47011
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 · uneditedPath Traversal in Ivanti Avalanche before version 6.4.5 allows a remote unauthenticated attacker to leak sensitive information
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 confidenceThis is a path traversal vulnerability in Ivanti Avalanche, a mobile device management solution. An unauthenticated remote attacker can manipulate file path inputs to access files outside the intended web root directory, potentially exposing sensitive system files, configuration data, or credentials.
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.5CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Identify Ivanti Avalanche installation versionLocate the installed Ivanti Avalanche version by checking the application itself (typically available in the admin UI under 'About' or 'System Information'), or check version files in the installation directory if you have server access. Compare this version number against the affected range: any version below 6.4.5 is vulnerable.Affected if The installed version is lower than 6.4.5
-
Confirm the web interface is exposedVerify that the Ivanti Avalanche web server (typically running on port 80/443 or a custom configured port) is accessible from the network. This vulnerability is exploitable remotely without authentication, so any exposed web interface is potentially vulnerable.Affected if The Ivanti Avalanche web interface is network-accessible (even on localhost)
-
Identify the file upload/download functionalityLocate any web endpoints that accept file path parameters, typically found in features related to file management, device configuration uploads, or resource distribution. These endpoints accept path input that could be manipulated for path traversal.Affected if File path parameters exist in any web-facing Avalanche functionality
Your environment is affected if you are running Ivanti Avalanche version lower than 6.4.5 AND the web interface is accessible, since the path traversal vulnerability can be exploited without authentication through file path handling endpoints.
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.5
Upgrade Ivanti Avalanche to version 6.4.5 or later. If immediate patching is not possible, implement web application firewall (WAF) rules to block path traversal patterns (e.g., ../, ..\) and restrict file access permissions on the server.
6.4.5
- Verify current Ivanti Avalanche version by checking the application or system information
- Download Ivanti Avalanche version 6.4.5 or later from the official Ivanti download portal or support site
- Review Ivanti Avalanche upgrade documentation for your specific deployment type
- Backup current Avalanche configuration, database, and any custom settings
- Stop the Avalanche server services before upgrading
- Install version 6.4.5 following standard Ivanti upgrade procedures
- Start Avalanche services and verify the application is running
- Validate that the path traversal vulnerability is remediated by confirming version 6.4.5 is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47011 — 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-47011 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