dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 8 Feb 2024. Known ransomware use
Endpoint Manager MobileApplication · Ivanti

CVE-2023-35082

CRITICAL · 9.8 CVSS v3.1 Published 2023-08-15
Fix available
A fix is available. Upgrade to 11.11.0 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware 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 authentication bypass vulnerability in Ivanti EPMM 11.10 and older, allows unauthorized users to access restricted functionality or resources of the application without proper authentication. This vulnerability is unique to CVE-2023-35078 announced earlier.

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

CVE-2023-35082 is an authentication bypass vulnerability in Ivanti Endpoint Manager Mobile (EPMM) versions 11.10 and older that allows unauthenticated attackers to bypass authentication mechanisms and access restricted application functionality or resources without proper credentials.

MitigationApply the vendor-provided patch or upgrade to a version newer than 11.10. Organizations should review Ivanti's security advisory for the specific fixed version and ensure the patch is applied in accordance with their change management processes.

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.11.0

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. Identify if Ivanti EPMM is installed
    Locate the Ivanti Endpoint Manager Mobile application on the system or check installed programs list for Ivanti EPMM components
    Affected if The application is present on the system
  2. Determine the installed version
    Access the EPMM admin interface or check system documentation to find the currently installed version number
    Affected if The installed version is any version lower than 11.11.0, including 11.10 and older releases
  3. Verify the management interface accessibility
    Confirm whether the EPMM web-based management console is reachable over the network from untrusted locations
    Affected if The management interface is exposed to the internet or untrusted networks without network access controls
  4. Review access logs for unauthorized sessions
    Examine EPMM access and audit logs for authentication events, particularly looking for successful administrative actions from unexpected IP addresses or at unusual times
    Affected if There are administrative actions or session creations that cannot be attributed to legitimate administrators

A system is affected if Ivanti Endpoint Manager Mobile is installed and the version is below 11.11.0, particularly if the management interface is network-accessible.

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.11.0 or later
Fixed in 11.11.0
Interim mitigation

Apply the vendor-provided patch or upgrade to a version newer than 11.10. Organizations should review Ivanti's security advisory for the specific fixed version and ensure the patch is applied in accordance with their change management processes.

Recommended fix High confidence

11.11.0 or later

  1. Check current Ivanti EPMM version by accessing the admin console or running:/mfs/bin/mobileiron -v
  2. Download Ivanti EPMM 11.11.0 or later from the official Ivanti portal (requires valid support contract)
  3. Review Ivanti upgrade documentation for 11.11.0 before proceeding
  4. Apply the upgrade following standard Ivanti EPMM upgrade procedures
  5. After upgrade, verify the version shows 11.11.0 or later and confirm admin console is accessible
  6. Validate that authentication is working correctly for all user roles

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

Fix this in Endpoint Manager Mobile Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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