CVE-2024-47008
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 · uneditedServer-side request forgery 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 confidenceIvanti Avalanche before version 6.4.5 contains a server-side request forgery (SSRF) vulnerability that allows remote unauthenticated attackers to make the server perform arbitrary HTTP requests to internal or external resources, potentially leaking sensitive information from internal services, metadata endpoints, or the local network.
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.
-
Determine Ivanti Avalanche installed versionLocate the Avalanche server version through the administration console (typically under Help > About or System > Status), or check the installation directory for version metadata files. If using the web interface, the version is often displayed on the login page or in the footer.Affected if The installed version is any release before 6.4.5 (e.g., 6.4.0 through 6.4.4, or earlier major versions)
-
Identify Avalanche server network accessibilityDetermine whether the Avalanche server is directly reachable from untrusted networks (the internet or DMZ). Check firewall rules, reverse proxy configurations, or cloud security groups that control access to the server's HTTP/HTTPS ports (typically 80/443 or custom ports).Affected if The server is exposed to the internet or untrusted networks without network-level filtering
-
Verify if unauthenticated HTTP request endpoints are reachableIdentify if the Avalanche web interface or API endpoints that handle external URL parameters are accessible without authentication. This typically involves checking whether the login/authentication layer is enforced on all paths and whether the server accepts URL parameters that could trigger outbound HTTP requests.Affected if The vulnerable SSRF endpoint is reachable without authentication and without additional access controls
A user is affected if their Ivanti Avalanche installation is version 6.4.4 or earlier AND the server or its web interface is network-accessible to untrusted parties.
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 upgrading is not possible, restrict network access to the Avalanche server and disable unnecessary HTTP request functionality at the network perimeter.
6.4.5
- Obtain the Ivanti Avalanche 6.4.5 upgrade package from the official Ivanti download portal or through your licensed support channel
- Review the Ivanti Avalanche upgrade guide for pre-upgrade requirements, including backup procedures
- Backup the current Avalanche installation, configuration files, and database
- Stop the Ivanti Avalanche services
- Install version 6.4.5 following the standard upgrade procedure
- Verify the upgrade was successful by checking the version number in the administration console
- Restart Avalanche services
- Confirm the SSRF vulnerability is remediated by verifying the affected component is no longer making unsanitized server-side requests
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-47008 — 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-47008 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