Threats / Ivanti / CVE-2024-21893
CVE-2024-21893
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
Ivanti Connect Secure, Policy and Neurons vulnerability
Ivanti Connect Secure, Policy Secure, and Neurons contain an SSRF vulnerability in the SAML component allowing unauthenticated access to restricted resources.
Verdict
Today item, not a backlog item.
A server-side request forgery flaw in SAML processing enables attackers to bypass authentication and reach internal systems. Active exploitation and ransomware deployment confirm critical risk.
CISA KEV Yes · 2024-01-315Ransomware use Flagged5EPSS 0.99999 (verify live)6Exploit Weaponized · public PoC7CVSS 8.23CISA SSVC Exploitation: active · Automatable: yes · Impact: partial4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
595 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-01-31), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.99999 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.2 (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N) · Affected: Ivanti, Connect Secure, Policy Secure, and Neurons. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.0, set at disclosure.
Weakness (CWE)
Mapped to CWE-918 Server-Side Request Forgery (SSRF).CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: partialCISA'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 functional/weaponized public exploit). Catalog entries: Metasploit module, 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 craft a malicious SAML request that causes the server to make requests to internal resources on my behalf.
Business
Attackers gain unauthenticated access to sensitive internal systems and data, bypassing security perimeters.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I use the SSRF to enumerate and access restricted administrative interfaces and configuration endpoints.
Business
Compromised administrative access enables lateral movement, privilege escalation, and system takeover.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage internal access to deploy ransomware payloads across the victim's infrastructure.
Business
Operations halt, data is encrypted, and organizations face extortion demands and recovery costs.
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
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by hackeroneCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.