dbcve.org
Endpoint Manager MobileApplication · Ivanti

CVE-2023-39337

CRITICAL · 9.1 CVSS v3.1 Published 2023-11-15
Fix available
A fix is available. Upgrade to 11.10.0.4 / 11.11.0.2 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
A security vulnerability in EPMM Versions 11.10, 11.9 and 11.8 older allows a threat actor with knowledge of an enrolled device identifier to access and extract sensitive information, including device and environment configuration details, as well as secrets. This vulnerability poses a serious security risk, potentially exposing confidential data and system integrity.

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

This is an information disclosure vulnerability in EPMM where the system fails to properly validate authorization when a request includes a valid enrolled device identifier. An attacker with knowledge of a device identifier can bypass authentication controls to access device configuration details and secrets stored in the system.

MitigationImplement proper authorization validation to ensure requests with device identifiers are also subject to full authentication and session verification before granting access to sensitive configuration data and secrets.

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:<= 11.9.0>= 11.10.0, < 11.10.0.4>= 11.11.0, < 11.11.0.2

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 the installed EPMM version
    Access the EPMM administration console or check the system information page to locate the exact version number of the installation
    Affected if The version falls within <= 11.9.0, >= 11.10.0 but < 11.10.0.4, or >= 11.11.0 but < 11.11.0.2
  2. Verify if device enrollment is active
    Check the EPMM console or database for the presence of enrolled mobile devices. This can be done through the admin interface under device management or by querying the device enrollment status
    Affected if There are enrolled devices in the system and the version is affected, making the vulnerability potentially exploitable
  3. Review access logs for device identifier patterns
    Examine EPMM server logs for requests that include device identifiers (device IDs, UDIDs, or similar identifiers) without proper session credentials or authentication tokens
    Affected if Logs show requests accessing device configuration endpoints using only a device identifier without corresponding authentication session validation
  4. Inspect API endpoint responses
    Test API endpoints that return device configuration data by supplying a known valid device identifier in the request. Observe whether the system returns sensitive configuration details or secrets without requiring full authentication
    Affected if The system returns device configuration details, secrets, or sensitive data when queried with just a valid device identifier without a valid authenticated session

A user is affected if their EPMM version is within the affected ranges AND the system has enrolled devices, allowing unauthorized access to device configuration data via device identifier injection.

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 11.10.0.4 / 11.11.0.2 or later
Fixed in 11.10.0.411.11.0.2
Interim mitigation

Implement proper authorization validation to ensure requests with device identifiers are also subject to full authentication and session verification before granting access to sensitive configuration data and secrets.

Recommended fix High confidence

Upgrade to EPMM 11.10.0.4, 11.11.0.2, or later

  1. 1. Identify the current EPMM version by accessing the admin console or checking system information
  2. 2. If running version <= 11.9.0, upgrade to version 11.11.0.2 or later
  3. 3. If running version 11.10.0 through 11.10.0.3, upgrade to version 11.10.0.4 or later
  4. 4. If running version 11.11.0 through 11.11.0.1, upgrade to version 11.11.0.2 or later
  5. 5. After upgrading, verify the patch was applied successfully and review system logs for any suspicious activity
  6. 6. Consider rotating any secrets that may have been exposed, as recommended by Ivanti security advisories

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

Fix this in Endpoint Manager Mobile Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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