CVE-2025-22464
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 untrusted pointer dereference vulnerability in Ivanti Endpoint Manager before version 2024 SU1 or before version 2022 SU7 allows an attacker with local access to write arbitrary data into memory causing a denial-of-service condition.
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 confidenceIvanti Endpoint Manager contains an untrusted pointer dereference vulnerability in versions prior to 2024 SU1 or 2022 SU7. An attacker with local access to the affected system can write arbitrary data into memory, leading to a denial-of-service condition. The vulnerability requires local physical or console access to exploit.
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
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/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.
-
Locate Ivanti Endpoint Manager installationCheck Program Files for 'Ivanti' folder, or look for the 'Endpoint Manager' service in Windows Services or the core application server componentAffected if The software is installed on the system
-
Identify the installed versionOpen the Ivanti Endpoint Manager administration console and navigate to Help > About, or check the registry under HKLM\SOFTWARE\LANDesk\LDMain\Core\Setup for a Version value, or inspect the core server component's version propertyAffected if Cannot determine the version from the installation
-
Compare version against affected rangesMatch the installed version (e.g., 2022.x, 2024.x) to the vulnerable ranges: versions prior to 2022, version 2022 (all patches), or version 2024 (all patches)Affected if Installed version is < 2022, equals 2022.x, or equals 2024.x (meaning not 2024 SU1 or later, and not 2022 SU7 or later)
-
Verify physical access controlsDocument whether the physical location housing the Endpoint Manager server and console access points has restricted entry controlsAffected if Physical and console access is not restricted (though version check is the primary indicator)
You are affected if Ivanti Endpoint Manager version is prior to 2022 SU7, or is version 2022.x or 2024.x without the SU1/SU7 security update applied.
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, 2022 SU7, or later to remediate this vulnerability. Restrict physical and console access to endpoint manager systems to reduce attack surface.
2024 SU1 or 2022 SU7
- Identify the current version of Ivanti Endpoint Manager installed in your environment
- If running version 2024, upgrade to 2024 SU1 (Service Update 1) or later
- If running version 2022, upgrade to 2022 SU7 (Service Update 7) or later
- If running a version earlier than 2022, plan an upgrade path to either 2022 SU7 or 2024 SU1
- Verify the upgrade was successful and the version matches the expected fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22464 — 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-22464 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