dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-8322

HIGH · 8.8 CVSS v3.1 Published 2024-09-10
Fix available
A fix is available. Upgrade to 2022 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Weak authentication in Patch Management of Ivanti EPM before 2022 SU6, or the 2024 September update allows a remote authenticated attacker to access restricted functionality.

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

Ivanti Endpoint Manager (EPM) contains weak authentication in its Patch Management component. A remote authenticated attacker can bypass authentication mechanisms to access restricted functionality. The vulnerability affects versions before 2022 SU6 or prior to the September 2024 update.

MitigationApply the vendor-supplied patch: update Ivanti EPM to version 2022 SU6 or later, or deploy the September 2024 update. Verify patch management functionality after updating.

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

CVSS:3.1/AV:N/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 Endpoint Manager installation
    Check for the Ivanti Endpoint Manager service or application. On Windows, look for the service named 'Ivanti Endpoint Manager' in Services console (services.msc) or check for installation in Program Files/Program Files (x86).
    Affected if The service or installation directory is not found, meaning EPM is not installed.
  2. Locate the installed version
    Open the Ivanti Endpoint Manager console and navigate to Help > About, or check the Windows Registry under HKLM\SOFTWARE\LANDesk\Manage\Setup for a Version value.
    Affected if Unable to retrieve version information.
  3. Compare version to affected ranges
    Evaluate the retrieved version against: any version before 2022, version 2022 (prior to SU6), or version 2024 (prior to September 2024 update). Note that version 2022 SU6 and later, or September 2024 and later, are NOT vulnerable.
    Affected if The installed version falls into any of these ranges: <2022, 2022 (pre-SU6), or 2024 (pre-September 2024).
  4. Verify Patch Management component status
    In the EPM console, navigate to Patch Management or Patch and Remediation component. Check if this module is configured, enabled, or accessible to users.
    Affected if Patch Management component is present and accessible in the environment.

If Ivanti EPM is installed with a version in the <2022, 2022 pre-SU6, or 2024 pre-September 2024 range AND the Patch Management component is accessible, the environment is affected by CVE-2024-8322.

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 the vendor-supplied patch: update Ivanti EPM to version 2022 SU6 or later, or deploy the September 2024 update. Verify patch management functionality after updating.

Recommended fix High confidence

2022 SU6 (Service Update 6) or 2024 September update

  1. 1. Identify the current Ivanti Endpoint Manager (EPM) version in use
  2. 2. For versions before 2022: upgrade to Ivanti Endpoint Manager 2022 Service Update 6 (SU6) or later
  3. 3. For version 2022: upgrade to 2022 SU6 or later
  4. 4. For version 2024: upgrade to the September 2024 update or later
  5. 5. Verify the upgrade was successful and test Patch Management functionality
  6. 6. Review user access controls and authentication settings in the Patch Management module
Caveat Review release notes for any configuration or compatibility changes when upgrading major versions

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

Fix this in Endpoint Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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