CVE-2023-35084
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 · uneditedUnsafe Deserialization of User Input could lead to Execution of Unauthorized Operations in Ivanti Endpoint Manager 2022 su3 and all previous versions, which could allow an attacker to execute commands remotely.
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 Endpoint Manager versions 2022 su3 and prior contain an unsafe deserialization vulnerability where user-supplied input is improperly handled during deserialization, enabling unauthenticated remote attackers to execute arbitrary commands on the affected system.
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< 2022= 2022CVSS 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 if Ivanti Endpoint Manager is installedLocate Ivanti Endpoint Manager on the system by checking installed programs, services, or the installation directory. Common installation paths may include C:\Program Files\Ivanti or C:\Program Files (x86)\Ivanti.Affected if Ivanti Endpoint Manager software is present on the system
-
Determine the installed versionCheck the exact version of Ivanti Endpoint Manager installed. This is typically available in the product UI (Help > About), in the Windows Programs and Features list, or in version files within the installation directory.Affected if The installed version is 2022 or any version prior to 2022 (including 2022 su3), which falls within the affected version range
-
Verify management console network exposureDetermine if the Ivanti Endpoint Manager management console is accessible from the network. Check firewall rules, reverse proxy configurations, or network ACLs that permit external access to port 443 or the console's HTTP/HTTPS endpoints.Affected if The management console is exposed to untrusted networks, as the vulnerability allows unauthenticated remote exploitation
-
Confirm deserialization feature is in useReview if the core Ivanti Endpoint Manager services are running and the management console functionality is operational. The unsafe deserialization flaw occurs when user-supplied input is processed during deserialization operations.Affected if The management console services are running and processing user-supplied data, which triggers the vulnerable deserialization code path
A system is affected if Ivanti Endpoint Manager version 2022 or any prior version is installed AND the management console is network-accessible, allowing unauthenticated attackers to trigger the unsafe deserialization.
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 · scoped2022
Apply vendor-provided security patches for Ivanti Endpoint Manager. If patching is not immediately possible, restrict network access to the management console and implement additional network segmentation to limit exposure.
Ivanti Endpoint Manager 2022 Service Update 4 (SU4) or later
- Identify current Ivanti Endpoint Manager version by checking the administration console or using the version check utility
- Download the latest Ivanti Endpoint Manager 2022 Service Update (SU4 or later) from the Ivanti portal or official download channels
- Review release notes to confirm the security fix for CVE-2023-35084 is included
- Schedule a maintenance window and create a full backup of the database and configuration
- Apply the upgrade following the standard Ivanti Endpoint Manager upgrade procedure
- Verify the upgrade was successful by checking the version number in the administration console
- Confirm the vulnerability is resolved by reviewing the release notes or consulting Ivanti knowledge base
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35084 — 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-35084 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