CVE-2023-28323
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 deserialization of untrusted data exists in EPM 2022 Su3 and all prior versions that allows an unauthenticated user to elevate rights. This exploit could potentially be used in conjunction with other OS (Operating System) vulnerabilities to escalate privileges on the machine or be used as a stepping stone to get to other network attached machines.
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 confidenceA critical deserialization of untrusted data vulnerability in Oracle Enterprise Performance Management (EPM) 2022 Su3 and prior versions allows unauthenticated attackers to deserialize malicious data, leading to privilege escalation. The flaw can be exploited remotely without credentials and potentially chain with other OS vulnerabilities for further system compromise.
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 installed EPM versionLocate the Oracle Enterprise Performance Management installation directory and check the version file or use the EPM System Configuration Manager to view the current version numberAffected if The installed version is 2022 Su3 or any version prior to the Su3 patch level
-
Verify EPM services are network-accessibleCheck if EPM HTTP/HTTPS services are listening on external interfaces or accessible from untrusted networks by reviewing network configuration and firewall rulesAffected if EPM services are exposed to unauthenticated network access without proper firewall restrictions
-
Identify deserialization endpointsReview EPM configuration files (particularly web.xml and any XML/Hessian serialization configurations in the deployment) for endpoints that accept serialized data without authenticationAffected if Deserialization endpoints are accessible without authentication and accept untrusted serialized data input
-
Check for exploitation indicatorsReview EPM server logs for unusual deserialization patterns, unexpected Java class loading, or signs of gadget chain exploitation in application logsAffected if Logs show suspicious deserialization activity or unexpected code execution patterns
If the installed EPM version is 2022 Su3 or prior and the services are network-accessible to unauthenticated users, the environment is affected by this CVE.
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 the latest Oracle EPM security patches (beyond Su3) or implement network segmentation/firewall rules to restrict access to EPM services until patching can be completed, as the unauthenticated nature makes immediate network-level mitigation critical.
Latest Ivanti Endpoint Manager version (post-2022 Su3)
- 1. Identify current Ivanti Endpoint Manager (EPM) version by checking the Console or installation
- 2. Download the latest Ivanti Endpoint Manager version from the official Ivanti portal (forums.ivanti.com)
- 3. Review release notes for security updates addressing CVE-2023-28323
- 4. Schedule a maintenance window for the upgrade
- 5. Back up the EPM database and configuration
- 6. Run the installer for the new version, following standard upgrade procedures
- 7. Verify the upgrade was successful and the service is running
- 8. Validate that the deserialization vulnerability is patched by confirming the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation12.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $16,896.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28323 — 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-28323 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