Threats / Ivanti / CVE-2024-8963
CVE-2024-8963
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Ivanti Cloud Services Appliance (CSA) vulnerability
Ivanti Cloud Services Appliance contains a path traversal vulnerability allowing unauthenticated remote access to restricted functionality. When chained with CVE-2024-8190, attackers can bypass authentication and execute arbitrary commands.
Verdict
Today item — known-exploited.
A critical unauthenticated remote code execution chain affecting Ivanti CSA. The path traversal enables initial access to restricted functions, which combined with authentication bypass leads to full appliance compromise and command execution.
CISA KEV Yes · 2024-09-195EPSS 0.98607 (verify live)6Exploit Public PoC7CVSS 9.43CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
560 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-09-19).
Probability (EPSS)
EPSS 0.98607 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.4 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L) · Affected: Ivanti, Cloud Services Appliance (CSA). Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-22 Path Traversal — weakness family: Path traversal / file.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog the same day the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I exploit the path traversal to access restricted appliance functionality without authentication.
Business
Attacker gains initial foothold on security-critical infrastructure with no credentials required.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I chain this with CVE-2024-8190 to bypass administrative authentication controls.
Business
Administrative protections are rendered ineffective, escalating from information access to full control.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute arbitrary commands on the compromised appliance.
Business
Complete system compromise enables data exfiltration, lateral movement, and persistent access to cloud infrastructure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05