basicsecurity.net
Proof, not just disclosure.
Threats / Ivanti / CVE-2024-29824
CVE-2024-29824 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Ivanti Endpoint Manager (EPM) vulnerability

Ivanti Endpoint Manager contains an unauthenticated SQL injection vulnerability in the Core server that allows network-adjacent attackers to execute arbitrary code.

Verdict

Today item — known-exploited.

SQL injection in EPM Core server enables unauthenticated remote code execution for attackers on the same network. High EPSS score and active exploitation indicate immediate risk to endpoint management infrastructure.

CISA KEV Yes · 2024-10-023EPSS 0.99951 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit 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
469 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-10-02).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.99951 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Ivanti, Endpoint Manager (EPM). Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-89 SQL Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-89 · SQL InjectionInjection
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

Front door — unauthenticated access narrative 1

Attacker
I craft malicious SQL queries targeting the EPM Core server without authentication.
Business
Attackers gain direct code execution on critical endpoint management infrastructure.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I execute arbitrary commands through the SQL injection to compromise the Core server.
Business
Entire endpoint fleet visibility and control is compromised, enabling lateral movement.
3

Lateral reach — past segmentation narrative 3

Attacker
I establish persistence and pivot to managed endpoints across the organization.
Business
Widespread endpoint compromise threatens data confidentiality and operational continuity.
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’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 469 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by hackerone (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by hackeroneCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.