CVE-2023-39335
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 · uneditedA security vulnerability has been identified in EPMM Versions 11.10, 11.9 and 11.8 and older allowing an unauthenticated threat actor to impersonate any existing user during the device enrollment process. This issue poses a significant security risk, as it enables unauthorized access and potential misuse of user accounts and 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 · high confidenceAn unauthenticated attacker can impersonate any existing user during the EPMM device enrollment process by bypassing authentication controls, allowing unauthorized access to user accounts and associated resources.
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< 11.9.0>= 11.10.0, < 11.10.0.4>= 11.11.0, < 11.11.0.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Ivanti EPMM is deployedIdentify whether Ivanti Endpoint Manager Mobile is installed in your environment. Check for EPMM server components, management console, or enrollment services.Affected if EPMM is present in the environment
-
Determine installed EPMM versionLocate the installed version of Ivanti Endpoint Manager Mobile through the EPMM admin console, system information page, or version display within the EPMM management interface. Compare the version number against the affected ranges: < 11.9.0, 11.10.0 through 11.10.0.3, or 11.11.0 through 11.11.0.1.Affected if The installed version falls within any of these vulnerable ranges: < 11.9.0, >= 11.10.0 and < 11.10.0.4, or >= 11.11.0 and < 11.11.0.2
-
Verify enrollment feature is enabledConfirm that the device enrollment functionality is active on the EPMM server. This is typically enabled by default for EPMM installations to allow mobile device onboarding.Affected if Device enrollment is enabled, which is the default configuration for EPMM
-
Assess network exposure of enrollment endpointDetermine whether the EPMM enrollment endpoint is accessible from untrusted networks or the internet. An unauthenticated attacker would need network access to the enrollment service to exploit this flaw.Affected if The enrollment endpoint is exposed to untrusted networks or the internet
You are affected if Ivanti EPMM is deployed with a version within the vulnerable ranges AND the enrollment feature is enabled, particularly if externally accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scoped11.9.011.10.0.411.11.0.2
Apply vendor-provided patches or upgrade EPMM to a version beyond the vulnerable releases (11.10, 11.9, 11.8) to remediate the enrollment authentication bypass.
Upgrade to EPMM 11.9.0, 11.10.0.4, or 11.11.0.2 (or later respective releases) depending on your current version branch
- 1. Identify the current version of Endpoint Manager Mobile (EPMM) by accessing the EPMM admin console or checking system information.
- 2. Determine which version range your current installation falls into: < 11.9.0, >= 11.10.0 but < 11.10.0.4, or >= 11.11.0 but < 11.11.0.2.
- 3. If running < 11.9.0, plan upgrade to version 11.9.0 or later.
- 4. If running >= 11.10.0 but < 11.10.0.4, plan upgrade to version 11.10.0.4 or later.
- 5. If running >= 11.11.0 but < 11.11.0.2, plan upgrade to version 11.11.0.2 or later.
- 6. Before upgrading, perform a complete backup of the EPMM configuration and database.
- 7. Review Ivanti upgrade documentation and release notes for your specific version path.
- 8. Execute the upgrade to the appropriate fixed version using Ivanti's recommended upgrade procedure.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39335 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-39335 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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