dbcve.org
Endpoint Manager MobileApplication · Ivanti

CVE-2024-36130

CRITICAL · 9.8 CVSS v3.1 Published 2024-08-07
Fix available
A fix is available. Upgrade to 12.1.0.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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 insufficient authorization vulnerability in web component of EPMM prior to 12.1.0.1 allows an unauthorized attacker within the network to execute arbitrary commands on the underlying operating system of the appliance.

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

EPMM versions prior to 12.1.0.1 contain an insufficient authorization vulnerability in the web component that allows unauthenticated attackers with network access to execute arbitrary commands on the underlying operating system of the appliance.

MitigationUpgrade EPMM to version 12.1.0.1 or later to remediate this vulnerability. If immediate patching is not possible, restrict network access to the EPMM web interface to trusted IPs only.

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 Manager MobileApplication
Affected:< 12.1.0.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 EPMM is installed
    Identify if Ivanti Endpoint Manager Mobile is installed on the system or accessible on the network. Look for EPMM-related processes, services, or the web application responding on common ports (typically 443 or 8443).
    Affected if EPMM software is found running on the system or accessible over the network.
  2. Determine the installed EPMM version
    Locate the installed version of Ivanti Endpoint Manager Mobile. This is typically accessible through the EPMM admin console, about page, or system information panel within the web interface. Alternatively, check the software inventory or installed packages on the host operating system.
    Affected if The installed version cannot be determined or is visible and is below 12.1.0.1.
  3. Verify the web component is enabled
    Confirm that the EPMM web component (the administrative web interface) is enabled and accessible. Check if the web service is running and responding to HTTP/HTTPS requests.
    Affected if The web component is enabled and accessible without authentication.
  4. Check network exposure of the web interface
    Determine if the EPMM web interface is exposed to untrusted network segments. Verify whether the web service is bound to all network interfaces or is accessible from outside trusted IP ranges.
    Affected if The web interface is accessible from untrusted networks or the internet.
  5. Compare version against affected range
    Review the identified EPMM version against the affected range: versions prior to 12.1.0.1 are vulnerable.
    Affected if The installed EPMM version is lower than 12.1.0.1 and the web component is exposed.

The environment is affected if EPMM is installed with a version prior to 12.1.0.1 and the web component is accessible over the network, allowing unauthenticated attackers to potentially execute commands.

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 12.1.0.1 or later
Fixed in 12.1.0.1
Interim mitigation

Upgrade EPMM to version 12.1.0.1 or later to remediate this vulnerability. If immediate patching is not possible, restrict network access to the EPMM web interface to trusted IPs only.

Recommended fix High confidence

12.1.0.1

  1. Backup the current EPMM configuration and data before initiating the upgrade
  2. Download the EPMM 12.1.0.1 (or later) update package from the Ivanti customer portal at portals.ivanti.com
  3. Access the EPMM admin console and navigate to System Settings > Maintenance > Software Update
  4. Upload and apply the 12.1.0.1 update following the on-screen prompts
  5. Allow the appliance to complete the upgrade process and reboot if required
  6. Verify the version shows 12.1.0.1 or later in the admin console
  7. Test that the web component and command execution functionality are working properly
Caveat Standard upgrade; review Ivanti release notes for any configuration or behavioral changes between your current version and 12.1.0.1

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

Fix this in Endpoint Manager Mobile Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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