CVE-2023-35081
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 path traversal vulnerability in Ivanti EPMM versions (11.10.x < 11.10.0.3, 11.9.x < 11.9.1.2 and 11.8.x < 11.8.1.2) allows an authenticated administrator to write arbitrary files onto the appliance.
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 confidenceIvanti EPMM contains a path traversal vulnerability allowing an authenticated administrator to write arbitrary files to the appliance filesystem. This occurs due to insufficient validation of file paths in the affected versions, enabling directory traversal sequences to bypass security controls.
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.0, < 11.8.1.2>= 11.9.0, < 11.9.1.2>= 11.10.0, < 11.10.0.3CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Determine installed Ivanti EPMM versionLog into the EPMM admin console and navigate to System Settings > Server or About page to view the installed version. Alternatively, check the Appliance Dashboard or run 'mvtctl --version' if SSH access is available.Affected if The installed version falls within these ranges: 11.8.0 to 11.8.1.1, 11.9.0 to 11.9.1.1, or 11.10.0 to 11.10.0.2.
-
Verify administrative access configurationReview the list of configured administrator accounts in the EPMM console under Administration > Administrators or similar. Confirm whether local accounts or external directory accounts (LDAP/AD) have administrator-level privileges.Affected if Any administrator-level account exists in the system, as authenticated admin access is required to exploit this path traversal flaw.
-
Identify exposed file upload or API endpointsExamine the EPMM configuration for file import features such as software distribution, policy import, or certificate upload. These are typically found under Software > Packages, Policies, or System > Import sections of the admin console.Affected if Any file upload or import functionality is accessible to administrators, as the path traversal vulnerability is triggered through insufficient path validation during file write operations.
-
Audit recent administrator activity logsReview administrator audit logs in the EPMM console under Reports > Audit Logs or Administration > Logs. Look for suspicious file write operations, especially those targeting system directories or unusual file paths.Affected if Any anomalous file write activities are present in the logs, indicating potential exploitation attempts.
You are affected if your EPMM version is 11.8.0 through 11.8.1.1, 11.9.0 through 11.9.1.1, or 11.10.0 through 11.10.0.2 and you have any administrator accounts configured with access to file upload or import features.
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.211.9.1.211.10.0.3
Apply vendor-supplied patches by upgrading to version 11.10.0.3, 11.9.1.2, or 11.8.1.2 or later. Restrict administrative access to trusted personnel and monitor for suspicious file write operations.
Upgrade to 11.8.1.2 or later (11.8.x branch), 11.9.1.2 or later (11.9.x branch), or 11.10.0.3 or later (11.10.x branch) - preferably the latest stable release in your respective branch
- 1. Identify the current installed version of Ivanti Endpoint Manager Mobile (EPMM) by checking the system administration console or using the product's version check feature.
- 2. Determine which version branch you are currently on (11.8.x, 11.9.x, or 11.10.x) to select the appropriate upgrade path.
- 3. If on version 11.8.x, upgrade to version 11.8.1.2 or later (preferably the latest 11.8.x stable release).
- 4. If on version 11.9.x, upgrade to version 11.9.1.2 or later (preferably the latest 11.9.x stable release).
- 5. If on version 11.10.x, upgrade to version 11.10.0.3 or later (preferably the latest 11.10.x stable release).
- 6. Download the upgrade package from the official Ivanti software download portal or authorized distribution channel.
- 7. Review the upgrade guide and release notes for any pre-upgrade requirements or migration procedures.
- 8. Perform a full backup of the EPMM configuration and data before initiating the upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35081 — 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-35081 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