dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-22058

HIGH · 7.8 CVSS v3.0 Published 2024-05-31
Fix available
A fix is available. Upgrade to after 2021.1 or later.
See remediation →
80/100
Remediation priority · High
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
A buffer overflow allows a low privilege user on the local machine that has the EPM Agent installed to execute arbitrary code with elevated permissions in Ivanti EPM 2021.1 and older.

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 buffer overflow vulnerability in Ivanti EPM (Endpoint Protection Manager) Agent allows an authenticated low-privilege local user to execute arbitrary code with elevated (SYSTEM/root) privileges. The vulnerability exists in the agent's handling of certain operations, likely within a privileged service component.

MitigationApply vendor patches for Ivanti EPM 2021.1 and older versions; upgrade to 2021.2 or later per vendor guidance. If patching is delayed, limit local physical access and monitor for suspicious process execution.

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:<= 2021.1

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

CVSS:3.0/AV:L/AC:L/PR:L/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. Confirm Ivanti EPM is installed
    Check installed software on the system for 'Ivanti Endpoint Manager', 'Ivanti EPM', or 'Endpoint Protection Manager'. On Windows, use Programs and Features or 'Get-WmiObject -Class Win32_Product'. On Linux, check package manager listings.
    Affected if Ivanti Endpoint Manager is present on the system
  2. Identify the installed Ivanti EPM version
    Locate the Ivanti Endpoint Manager version information. Check the application properties, registry keys under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, or the core server/admin console for version details.
    Affected if The installed version is 2021.1 or any version lower than 2021.2
  3. Verify the EPM Agent service is running
    Confirm the Ivanti EPM Agent service is active. On Windows, run 'Get-Service' or check Services.msc for 'Endpoint Protection Manager Agent' or similar named service.
    Affected if The agent service is running and the version is 2021.1 or below
  4. Assess local user access context
    Determine if low-privilege local users have authenticated access to the system. This vulnerability requires an authenticated local user account.
    Affected if Low-privilege local user accounts exist and can log in to the system where vulnerable EPM is installed

You are affected if Ivanti Endpoint Manager version 2021.1 or below is installed with the agent service running on a system where local users can authenticate.

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 a release after 2021.1
Interim mitigation

Apply vendor patches for Ivanti EPM 2021.1 and older versions; upgrade to 2021.2 or later per vendor guidance. If patching is delayed, limit local physical access and monitor for suspicious process execution.

Recommended fix Moderate confidence

Upgrade to EPM 2022 or later (such as 2022.1, 2023, or latest supported release)

  1. 1. Identify the current Ivanti Endpoint Manager version installed in your environment
  2. 2. Review Ivanti Knowledge Base and support portals for the specific patch or fixed release addressing CVE-2024-22058
  3. 3. Schedule a maintenance window for the upgrade process
  4. 4. Back up the EPM database and configuration before proceeding
  5. 5. Upgrade Ivanti Endpoint Manager to version 2022 or later (2022.1, 2023, or latest supported release)
  6. 6. Verify the upgrade completed successfully
  7. 7. Confirm the EPM Agent service is running and functional
  8. 8. Test endpoint management functionality to ensure normal operations
Caveat Review release notes for database schema changes and ensure compatibility with existing integrations/third-party tools before upgrading

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

Fix this in Endpoint Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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