CVE-2024-47010
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 bypass authentication.
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 · moderate confidenceA path traversal vulnerability in Ivanti Avalanche before version 6.4.5 allows a remote unauthenticated attacker to bypass authentication. The vulnerability can be exploited by crafting malicious path traversal sequences in HTTP requests to access restricted resources or authentication mechanisms without valid 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Determine Ivanti Avalanche installed versionLocate the installed Ivanti Avalanche instance and retrieve its version number. This is typically available in the application itself, an about page, or installation metadata.Affected if The installed version is lower than 6.4.5 (for example, 6.4.0, 6.3.x, or earlier)
-
Identify Avalanche web interface exposureDetermine if the Ivanti Avalanche web interface or API endpoints are accessible from the network. Check firewall rules, reverse proxies, or direct binding configurations.Affected if The web interface is externally accessible and the version is below 6.4.5
-
Verify authentication mechanism is in useConfirm that the Avalanche application uses its native authentication to protect access. Attempt to access the login page or protected resources to confirm authentication is enforced.Affected if Authentication can be bypassed due to the path traversal flaw and the version is below 6.4.5
You are affected if Ivanti Avalanche is installed and the version is below 6.4.5, especially if the web interface is network-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.5
Upgrade Ivanti Avalanche to version 6.4.5 or later to remediate this vulnerability. If immediate patching is not possible, restrict network access to the Avalanche management interface and monitor for unusual path traversal patterns in requests.
6.4.5
- Download Ivanti Avalanche version 6.4.5 or later from the official Ivanti download portal
- Review the upgrade documentation for Avalanche 6.4.5
- Back up the current Avalanche configuration and database
- Install version 6.4.5 following the standard upgrade procedure
- Verify the installation completed successfully
- Confirm the path traversal vulnerability is remediated by testing authentication mechanisms
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47010 — 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-47010 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