CVE-2023-35078
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 · uneditedAn authentication bypass vulnerability in Ivanti EPMM allows unauthorized users to access restricted functionality or resources of the application without proper authentication.
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 confidenceThis is an authentication bypass vulnerability in Ivanti EPMM (Enterprise Policy and Patch Manager) that allows unauthenticated attackers to bypass authentication mechanisms and access restricted administrative functions and sensitive resources within the application. The critical CVSS score of 9.8 indicates the vulnerability is remotely exploitable without user interaction and provides complete compromise of confidentiality, integrity, and availability.
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.8.1.1>= 11.9.0, < 11.9.1.1>= 11.10, < 11.10.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.
-
Identify the installed EPMM versionAccess the Ivanti Endpoint Manager Mobile admin console or API endpoint that displays the product version information. This is typically found in the About or System Information section of the management interface.Affected if The installed version is less than 11.8.1.1, OR is 11.9.0 through 11.9.1.0, OR is 11.10.0.0 or 11.10.0.1 (any version matching the ranges: < 11.8.1.1, >= 11.9.0 and < 11.9.1.1, >= 11.10 and < 11.10.0.2)
-
Verify EPMM management interface is network accessibleDetermine if the EPMM web console or API endpoints are reachable from network locations outside the trusted internal network. This may involve reviewing firewall rules, reverse proxy configurations, or network ACLs that control access to EPMM ports.Affected if The EPMM management interface is exposed to untrusted networks or the internet without proper access controls
-
Review administrative access logs for anomalous activityExamine EPMM audit logs and access logs for unauthorized administrative actions, particularly those originating from unexpected IP addresses or occurring at unusual times without corresponding successful login events.Affected if There are administrative actions logged that were not performed by known legitimate administrators, or administrative actions without preceding successful authentication records
A user is affected if their EPMM installation version falls within any of the vulnerable ranges AND the management interface is accessible to potential attackers, regardless of whether signs of exploitation are observed.
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.8.1.111.9.1.111.10.0.2
Apply the vendor-provided patch or update to Ivanti EPMM immediately to remediate the authentication bypass. Until patched, restrict network exposure of the affected system and monitor for unauthorized access attempts in logs.
11.8.1.1 (or later 11.8.x), 11.9.1.1 (or later 11.9.x), or 11.10.0.2 (or later 11.10.x) depending on your current branch
- 1. Identify the current installed version of Ivanti Endpoint Manager Mobile (EPMM) in your environment
- 2. Based on your current major version, determine the appropriate upgrade path: if on 11.7.x or earlier, upgrade to 11.8.1.1 or later; if on 11.9.0.x, upgrade to 11.9.1.1 or later; if on 11.10.0.0 or 11.10.0.1, upgrade to 11.10.0.2 or later
- 3. Review Ivanti's official upgrade documentation and release notes for the target version
- 4. Perform a backup of the current EPMM configuration and database
- 5. Schedule a maintenance window for the upgrade procedure
- 6. Download the appropriate patched version from Ivanti's customer portal or authorized distribution channel
- 7. Follow Ivanti's standard upgrade procedure for EPMM (typically involves stopping services, running the installer, and verifying the upgrade)
- 8. After upgrade, verify that the EPMM web interface is accessible and functioning normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35078 — 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-35078 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