dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2025-6996

HIGH · 8.4 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 2022 or later.
See remediation →
86/100
Remediation priority · High
Zero-click

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 · unedited
Improper use of encryption in the agent of Ivanti Endpoint Manager before version 2024 SU3 and 2022 SU8 Security Update 1 allows a local authenticated attacker to decrypt other users’ passwords.

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 confidence

Improper encryption implementation in the Ivanti Endpoint Manager agent before version 2024 SU3 and 2022 SU8 Security Update 1 allows a locally authenticated attacker to decrypt passwords belonging to other users on the same system, enabling local privilege escalation through password theft.

MitigationUpgrade Ivanti Endpoint Manager agent to version 2024 SU3 or 2022 SU8 Security Update 1 or later to remediate the weak encryption. Consider rotating compromised credentials after applying the update.

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
Endpoint ManagerApplication
Affected:< 2022= 2022= 2024

CVSS 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
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Ivanti Endpoint Manager agent is installed
    Check for the presence of the Ivanti Endpoint Manager agent service or executable on the system. Common installation paths include C:\Program Files\Ivanti or C:\Program Files (x86)\Ivanti. Look for services named 'Ivanti Endpoint Manager' or executables such as 'LDISCN32.EXE', 'LDPROV.EXE', or 'CoreService.exe'.
    Affected if The Ivanti Endpoint Manager agent is installed on the system.
  2. Determine the installed version of Ivanti Endpoint Manager
    Locate the agent executable (typically in the installation directory) and check its version property, or query the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Ivanti Endpoint Manager entries to retrieve the installed version number.
    Affected if The installed version cannot be determined or the agent is present but version is unknown.
  3. Compare installed version against vulnerable ranges
    Review the version retrieved from the previous step. The vulnerable versions are: any version below 2022, version 2022 (all SU releases before SU8 Security Update 1), and version 2024 (all SU releases before SU3). Versions 2024 SU3 and later, or 2022 SU8 Security Update 1 and later, are not affected.
    Affected if The installed version is 2022 (any update before SU8 Security Update 1), 2024 (any update before SU3), or any version below 2022.
  4. Verify password storage or encryption configuration exists
    Inspect the Ivanti Endpoint Manager agent configuration and data directories for files containing stored credentials or password hashes. The vulnerability allows decryption of passwords belonging to other users on the same system, indicating insecure storage of credentials accessible to multiple authenticated users.
    Affected if Credential storage files or configurations exist and are accessible to locally authenticated users on the system.

The system is affected if Ivanti Endpoint Manager agent is installed with a version in the 2022 or 2024 lines before the security updates, or any version below 2022, and password storage files are accessible to locally authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2022 or later
Fixed in 2022
Interim mitigation

Upgrade Ivanti Endpoint Manager agent to version 2024 SU3 or 2022 SU8 Security Update 1 or later to remediate the weak encryption. Consider rotating compromised credentials after applying the update.

Recommended fix High confidence

2024 SU3 or 2022 SU8 Security Update 1 (depending on your current major version)

  1. 1. Verify current Ivanti Endpoint Manager version by checking the console or agent information
  2. 2. Back up the Ivanti Endpoint Manager database and configuration before performing the upgrade
  3. 3. Download the appropriate security update: 2024 SU3 for customers on version 2024, or 2022 SU8 Security Update 1 for customers on version 2022
  4. 4. Apply the security update following Ivanti's standard patch deployment procedures
  5. 5. Verify the update was successfully applied by checking the agent and console version information
  6. 6. Test that password functionality works correctly post-update
Caveat Standard upgrade precautions apply: backup before upgrading, test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Endpoint Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6996 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-6996 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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