dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2025-6995

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 due to cryptographic weaknesses in the credential storage mechanism.

MitigationApply the security updates (2024 SU3 or 2022 SU8 Security Update 1 or later) to upgrade the Ivanti Endpoint Manager agent and remediate the improper encryption.

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. Confirm Ivanti Endpoint Manager agent installation
    Check for the Ivanti Endpoint Manager agent installation on the system. Look for the agent service or executable, typically installed in Program Files\Ivanti\ or check Windows Services for 'Ivanti Endpoint Manager' or 'LANDesk' related services.
    Affected if The agent is installed and running on the system.
  2. Identify the installed version
    Locate the agent version information. Right-click the agent executable (typically named something like 'WdService.exe' or 'LDISERV32.exe' in the Ivanti installation directory) and view Properties, or query the service information via command line using 'sc query' or 'Get-Service' in PowerShell to retrieve version details.
    Affected if The version is 2024 (before SU3) or 2022 (before SU8 Security Update 1). Versions prior to 2022 are also affected.
  3. Verify credential storage is in use
    Check if the Endpoint Manager agent has been configured to manage credentials. Look for configured user accounts, saved passwords, or credential policies within the agent console, or check for stored credential files in the agent's data directory.
    Affected if The agent has stored credentials, passwords, or authentication configurations for users or network resources.
  4. Check for vulnerable credential storage files
    Inspect the agent's credential storage location. The agent stores credentials in encrypted format in its configuration or database files within the installation directory. Look for files like '*.db', 'cred*.*', or XML configuration files that may contain encrypted password data.
    Affected if Credential storage files exist and contain encrypted passwords that could be decrypted by a locally authenticated attacker.

A system is affected if the Ivanti Endpoint Manager agent is installed with version 2024 (before SU3), 2022 (before SU8 SU1), or earlier, and the agent stores or manages credentials that could be accessed by a local authenticated user.

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

Apply the security updates (2024 SU3 or 2022 SU8 Security Update 1 or later) to upgrade the Ivanti Endpoint Manager agent and remediate the improper encryption.

Recommended fix Moderate confidence

2024 SU3 (for 2024.x users) or 2022 SU8 Security Update 1 (for 2022.x users)

  1. Identify the current version of Ivanti Endpoint Manager by checking the agent or server console
  2. Determine your upgrade path: if on a version < 2022 or on 2022, target 2022 SU8 Security Update 1; if on 2024, target 2024 SU3
  3. Review Ivanti's official upgrade documentation and release notes for the target version
  4. Create a complete backup of the current Endpoint Manager configuration and database
  5. Test the upgrade in a non-production environment first to verify compatibility
  6. Schedule a maintenance window for the upgrade process
  7. Apply the upgrade to the Endpoint Manager server following Ivanti's documented procedures
  8. After upgrade, verify the agent versions and ensure all clients are updated to the patched version
Caveat Standard upgrade considerations apply - review release notes for deprecations or configuration changes specific to your version path

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

Fix this in Endpoint Manager Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6995 — 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-6995 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