dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-37397

HIGH · 8.2 CVSS v3.1 Published 2024-09-12
Fix available
A fix is available. Upgrade to 2022 or later.
See remediation →
91/100
Remediation priority · Urgent
High EPSS 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
An External XML Entity (XXE) vulnerability in the provisioning web service of Ivanti EPM before 2022 SU6, or the 2024 September update allows a remote unauthenticated attacker to leak API secrets.

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

Ivanti EPM contains an XXE vulnerability in its provisioning web service that allows remote unauthenticated attackers to inject malicious XML external entity references, enabling disclosure of sensitive API secrets stored on the system.

MitigationApply the vendor-supplied patch (2022 SU6 or 2024 September update) to remediate the XXE vulnerability. Consider disabling the provisioning web service if not required and implementing XML parser hardening.

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

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
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 EPM version
    Check the installed Ivanti Endpoint Manager version through the product UI, registry, or installation directory. Common locations include the About section in the console or checking installed programs.
    Affected if The installed version is 2022 or any version prior to 2022 (any version < 2022). Versions 2023 and later are not affected.
  2. Locate provisioning web service
    Identify whether the provisioning web service component is installed and running. This is typically a web service component accessible via IIS or the application's web interface.
    Affected if The provisioning web service is installed and running on the system.
  3. Verify web service accessibility
    Determine if the provisioning web service endpoint is accessible remotely or locally. Check if the service listens on typical ports used by Ivanti EPM (often ports 80/443 or custom ports).
    Affected if The provisioning web service endpoint is exposed and reachable.
  4. Check XML parser configuration
    If accessible, examine the XML parser settings for the provisioning web service. The XXE vulnerability exists when the parser is configured to process external entity references.
    Affected if The XML parser accepts external entity references without proper disabling of DTD processing.

You are affected if the installed Ivanti Endpoint Manager version is 2022 or earlier AND the provisioning web service is enabled and processing XML requests.

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 (2022 SU6 or 2024 September update) to remediate the XXE vulnerability. Consider disabling the provisioning web service if not required and implementing XML parser hardening.

Recommended fix High confidence

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

  1. 1. Identify the current Ivanti Endpoint Manager version by checking the server administration console or help/about section
  2. 2. Create a full backup of the Ivanti EPM database and configuration settings before proceeding with any update
  3. 3. Download the applicable update: either Ivanti EPM 2022 SU6 (Service Update 6) for the 2022 version line, or the 2024 September update for newer versions
  4. 4. Apply the update by running the installer on the Ivanti EPM server, following the standard upgrade procedure documented in the Ivanti knowledge base
  5. 5. After installation completes, verify the version has been updated and confirm the provisioning web service is functioning normally
  6. 6. Test that XML-based operations in the provisioning web service work correctly to ensure no regression

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-37397 — 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-37397 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