dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-8441

MEDIUM · 6.7 CVSS v3.1 Published 2024-09-10
Fix available
A fix is available. Upgrade to 2022 or later.
See remediation →
69/100
Remediation priority · Elevated
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
An uncontrolled search path in the agent of Ivanti EPM before 2022 SU6, or the 2024 September update allows a local authenticated attacker with admin privileges to escalate their privileges to SYSTEM.

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 confidence

An uncontrolled search path (likely DLL hijacking) in the Ivanti Endpoint Policy Manager (EPM) agent allows a local authenticated administrator to execute arbitrary code as the SYSTEM user by causing the agent to load a malicious library from an attacker-controlled location.

MitigationApply vendor updates: either version 2022 SU6 or the 2024 September update for Ivanti EPM to remediate this 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 ManagerApplication
Affected:< 2022= 2022= 2024

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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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. Verify Ivanti Endpoint Policy Manager (EPM) agent is installed
    Check Windows Programs and Features for 'Ivanti Endpoint Manager' or 'LANDesk Management' entries, or query the registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for related product names
    Affected if The product is not found in installed programs
  2. Identify the installed EPM version
    Check the version in Programs and Features, or query the registry key for the installed version, or locate the main agent executable (typically in C:\Program Files\Ivanti\ or C:\Program Files\LANDesk\) and view its file properties
    Affected if The version displayed is 2022 (any release) or 2024 (any release) or any version prior to 2022
  3. Confirm the EPM agent service runs with elevated privileges
    Open Services, locate the Ivanti/LANDesk agent service (commonly 'LDClient' or 'Endpoint Manager Agent'), right-click and view Properties, check the 'Log on as' account
    Affected if The service runs as 'Local System' or 'NT AUTHORITY\SYSTEM' account
  4. Verify the agent executable search path is writable by standard users
    Use Process Monitor or examine the agent service executable path permissions to determine if non-admin users can write to directories in the executable's load path
    Affected if Authenticated users have write access to directories from which the agent loads libraries

A user is affected if Ivanti Endpoint Policy Manager agent is installed and running with SYSTEM privileges, and the installed version falls within 2022 or 2024 (any release) or is earlier than 2022.

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
Upgrade available Upgrade to 2022 or later
Fixed in 2022
Interim mitigation

Apply vendor updates: either version 2022 SU6 or the 2024 September update for Ivanti EPM to remediate this vulnerability.

Recommended fix Moderate confidence

2022 SU6 (for 2022 branch) or September 2024 update (for 2024 branch)

  1. 1. Identify the current version of Ivanti Endpoint Manager (EPM) by checking the agent or console
  2. 2. Review the Ivanti knowledge base and release notes at forums.ivanti.com for detailed upgrade instructions
  3. 3. For version 2022: Upgrade to 2022 SU6 (Service Update 6) which contains the fix
  4. 4. For version 2024: Apply the September 2024 update which contains the fix
  5. 5. Follow standard upgrade procedures: backup configuration data and create a system restore point before applying updates
  6. 6. Apply the update through the Ivanti EPM console or standard deployment method
  7. 7. After upgrade, verify the version reflects the patched release and confirm services start correctly
  8. 8. Test that the EPM agent runs correctly and performs as expected
Caveat Review release notes for any known compatibility issues or required configuration changes before upgrading

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

Fix this in Endpoint Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8441 — 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-8441 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