Endpoint Manager MobileApplication · Ivanti

CVE-2024-36132

HIGH · 7.5 CVSS v3.1 Published 2024-08-07
Fix available
A fix is available. Upgrade to 12.1.0.1 or later.
See remediation →
84/100
Remediation priority · High
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
Insufficient verification of authentication controls in EPMM prior to 12.1.0.1 allows a remote attacker to bypass authentication and access sensitive resources.

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

EPMM versions prior to 12.1.0.1 contain insufficient verification of authentication controls, allowing a remote attacker to bypass the authentication mechanism entirely and access sensitive resources without valid credentials.

MitigationUpgrade EPMM to version 12.1.0.1 or later to implement proper authentication verification. If immediate upgrade is not feasible, restrict network access to the EPMM interface and monitor for unauthorized access attempts.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Confirm EPMM is deployed
    Check for Ivanti Endpoint Manager Mobile installation by reviewing installed software on servers, searching for 'EPMM' or 'Endpoint Manager Mobile' in your asset inventory or configuration management system
    Affected if EPMM software is found in the environment
  2. Identify EPMM version
    Access the EPMM admin console or check the software version through the application's 'About' or 'System Information' page, typically found under Settings or Help sections
    Affected if Version is displayed as anything less than 12.1.0.1
  3. Verify version via command line or config file
    If available, check the EPMM installation directory for version files, or run 'epmm --version' or similar diagnostic command documented in the product admin guide
    Affected if Returned version number is below 12.1.0.1
  4. Confirm authentication interface is accessible
    Test access to the EPMM web login page or API endpoints from external network locations to determine if the authentication mechanism can be reached
    Affected if EPMM login interface is reachable from untrusted networks

If EPMM is installed with a version lower than 12.1.0.1 and the authentication interface is network-accessible, the environment is vulnerable to authentication bypass.

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 implement proper authentication verification. If immediate upgrade is not feasible, restrict network access to the EPMM interface and monitor for unauthorized access attempts.

Recommended fix Moderate confidence

12.1.0.1

  1. Obtain the EPMM 12.1.0.1 or later version from the official Ivanti download portal or support channels
  2. Review the official Ivanti upgrade documentation for Endpoint Manager Mobile
  3. Ensure you have a complete backup of the current EPMM installation and database
  4. Test the upgrade in a non-production environment before deploying to production
  5. Execute the upgrade following Ivanti's documented upgrade procedure
  6. After upgrade, verify that authentication controls are functioning correctly
  7. Confirm the version by checking the EPMM admin console or system information

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
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
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,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36132 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-36132 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