dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-8320

MEDIUM · 5.3 CVSS v3.1 Published 2024-09-10
Fix available
A fix is available. Upgrade to 2022 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Missing authentication in Network Isolation of Ivanti EPM before 2022 SU6, or the 2024 September update allows a remote unauthenticated attacker to spoof Network Isolation status of managed devices.

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

Missing authentication in Network Isolation of Ivanti Endpoint Manager allows a remote unauthenticated attacker to spoof the network isolation status of managed devices, potentially causing devices to appear isolated or unisolated when they are not.

MitigationApply the vendor-supplied updates: Ivanti EPM 2022 SU6 or later, or the 2024 September update.

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

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

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. Identify Ivanti Endpoint Manager installation
    Check for Ivanti Endpoint Manager (EPM) installation by looking in Windows Programs and Features, or checking for the Core Server service in Services.msc named 'LANDesk Management Server' or similar LANDESK/LANDesk components
    Affected if The product is installed on the system
  2. Determine installed EPM version
    Open Windows Registry at HKLM\SOFTWARE\LANDesk\ManagementSuite\Setup or check the Core Server version via the EPM console under Help > About, or locate version in uninstall information
    Affected if Version is 2022 (any patch level) or 2024 (any patch level), or any version prior to 2022
  3. Verify Network Isolation module is enabled
    Open EPM console, navigate to Network Access Protection or Network Isolation settings (typically under Configure > Network > Network Isolation), or check registry key HKLM\SOFTWARE\LANDesk\ManagementSuite\Security\NetworkIsolation for enabled status
    Affected if Network Isolation feature is configured and enabled on the server
  4. Check Network Isolation policy configuration
    In EPM console, examine the Network Isolation policies under the appropriate policy section to confirm isolation rules are defined for client devices
    Affected if Network Isolation policies exist and are applied to devices

A system is affected if it runs Ivanti Endpoint Manager version 2022, 2024, or any version prior to 2022 AND has the Network Isolation feature enabled.

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 updates: Ivanti EPM 2022 SU6 or later, or the 2024 September update.

Recommended fix Moderate confidence

Ivanti EPM 2022 SU6 or later; or the 2024 September update (or later)

  1. 1. Identify the current installed version of Ivanti Endpoint Manager (EPM)
  2. 2. If running a version before 2022 SU6, upgrade to Ivanti EPM 2022 SU6 (or later 2022 release that includes SU6)
  3. 3. If running version 2022 (without SU6), apply the SU6 update or upgrade to 2022 SU6
  4. 4. If running 2024 version before September 2024, upgrade to the September 2024 update or later
  5. 5. Verify the upgrade was successful and Network Isolation functionality is working properly
  6. 6. Review Network Isolation policies to ensure they are functioning as expected post-upgrade
Caveat Review release notes for 2022 SU6 and 2024 September update for any feature changes or migration requirements 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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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