CVE-2025-22458
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 · uneditedDLL hijacking in Ivanti Endpoint Manager before version 2024 SU1 or before version 2022 SU7 allows an authenticated attacker to escalate to System.
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 confidenceDLL hijacking vulnerability in Ivanti Endpoint Manager allows an authenticated attacker to place a malicious DLL in a path where the application loads DLLs from, enabling code execution with System-level privileges. The attacker needs valid credentials to authenticate to the system before exploiting this vulnerability.
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= 2022= 2024CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 Ivanti Endpoint Manager versionLocate the installed version of Ivanti Endpoint Manager in your environment using your software inventory or system information tools. Common methods include checking the application itself, reviewing installed software listings, or querying the configuration database.Affected if The installed version is any release in the 2022 or 2024 major version lines (including 2022 and 2024), or any version prior to 2022.
-
Confirm application runs with elevated privilegesVerify that the Ivanti Endpoint Manager service or process runs under a high-privilege account such as System or a service account with elevated rights.Affected if The service runs with System-level or equivalent elevated privileges, which is the default configuration for this application.
-
Assess authenticated user access to systemDetermine whether standard authenticated users (non-administrators) have the ability to write files to directories from which Ivanti Endpoint Manager loads DLLs, or whether only privileged administrators have such access.Affected if Authenticated users with lower privileges can write to DLL load paths used by the application, creating the condition for DLL hijacking.
You are affected if your Ivanti Endpoint Manager version is 2022, 2024, or any version prior to 2022, and the application loads DLLs from a location writable by authenticated users.
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
Upgrade Ivanti Endpoint Manager to version 2024 SU1 or later, or version 2022 SU7 or later, depending on the current major version branch in use.
2024 SU1 or 2022 SU7
- Backup the Ivanti Endpoint Manager database and configuration before proceeding
- Verify that your system meets the hardware and software requirements for the target version
- Download the applicable security update: either Ivanti Endpoint Manager 2024 SU1 or 2022 SU7 from the official Ivanti portal
- Stop all Ivanti Endpoint Manager services on the server
- Run the installer with administrative privileges, following the on-screen prompts
- Allow the installation to complete and ensure all files are updated
- Restart the Ivanti Endpoint Manager services
- Verify the upgrade was successful by checking the console and confirming the version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22458 — 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-2025-22458 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