dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 10 Oct 2024.
Endpoint Manager Cloud Services ApplianceApplication · Ivanti

CVE-2024-8963

CRITICAL · 9.1 CVSS v3.1 Published 2024-09-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click

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 · unedited
Path Traversal in the Ivanti CSA before 4.6 Patch 519 allows a remote unauthenticated attacker to access restricted functionality.

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 confidence

A path traversal vulnerability in Ivanti Connect Secure (CSA) versions before 4.6 Patch 519 allows remote unauthenticated attackers to access restricted functionality by manipulating file path inputs in HTTP requests.

MitigationApply Ivanti CSA version 4.6 Patch 519 or later to remediate the path traversal vulnerability.

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
Endpoint Manager Cloud Services ApplianceApplication
Affected:= 4.6

CVSS 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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Ivanti CSA is deployed
    Access the web admin interface or check system inventory for 'Ivanti Cloud Service Appliance' or 'Ivanti CSA' product installation
    Affected if The product is not Ivanti Cloud Service Appliance - this CVE does not apply
  2. Determine the installed CSA version
    Log into the CSA web admin console and navigate to the About or System Information page, or run 'csa --version' via CLI if available, to obtain the exact version number
    Affected if Version is not 4.6 - only version 4.6 is affected by this specific CVE
  3. Confirm patch level for version 4.6
    In the CSA admin interface, check the installed patches or patch history section to see if Patch 519 (or higher) is applied
    Affected if Version is 4.6 and Patch 519 or later is NOT installed - the vulnerability is present
  4. Inspect web server access logs for traversal attempts
    Review CSA web server access logs (typically in /var/log or the CSA logs directory) for requests containing '..' sequences in URLs, such as '../' or '..%2F' patterns
    Affected if Unfamiliar or suspicious traversal sequences appear in logs - indicates potential exploitation attempts
  5. Verify web interface exposure
    Check if the CSA web interface is accessible from untrusted networks (internet-facing) using a browser to confirm the attack surface
    Affected if The web interface is exposed to unauthenticated remote attackers - the path traversal can be exploited remotely

You are affected if you have Ivanti CSA version 4.6 installed without Patch 519 or higher, and the web interface is accessible (even internally) since the flaw allows remote unauthenticated path traversal.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Ivanti CSA version 4.6 Patch 519 or later to remediate the path traversal vulnerability.

Recommended fix High confidence

4.6 Patch 519

  1. 1. Back up the current Ivanti CSA configuration and data before applying any updates
  2. 2. Download Ivanti CSA version 4.6 Patch 519 from the official Ivanti download portal or support site
  3. 3. Follow Ivanti's standard patch deployment procedure for the Cloud Services Appliance
  4. 4. After patch installation, verify the patch version shows 4.6 Patch 519 in the system information
  5. 5. Test that the path traversal vulnerability is no longer exploitable

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Endpoint Manager Cloud Services Appliance Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8963 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-8963 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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