CVE-2025-62384
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 · uneditedSQL injection in Ivanti Endpoint Manager before version 2024 SU5 allows a remote authenticated attacker to read arbitrary data from the database.
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 confidenceSQL injection vulnerability in Ivanti Endpoint Manager prior to version 2024 SU5 allows a remote authenticated attacker to execute arbitrary SQL queries and read sensitive data from the database.
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< 2024= 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Ivanti Endpoint Manager installationLocate the Ivanti Endpoint Manager application on the system or check installed programs list. Look for core application files typically in C:\Program Files\Ivanti or C:\Program Files (x86)\Ivanti, or check the Windows Services list for 'Ivanti Endpoint Manager' or 'LDMS' services.Affected if Ivanti Endpoint Manager is installed and the version is prior to 2024 SU5, or if the version is exactly 2024 without SU5 applied.
-
Determine installed version numberOpen the Ivanti Endpoint Manager console, go to Help > About, or check the Windows Services description for the version string. Alternatively, check registry keys under HKLM\SOFTWARE\LANDesk\LDWS or HKLM\SOFTWARE\Ivanti for the version information.Affected if The reported version is any build prior to 2024 SU5 (e.g., 2024, 2024 SU1, SU2, SU3, SU4) or if the version cannot be determined but matches the product name.
-
Verify remote access configurationCheck if the Ivanti Endpoint Manager web console or management port (typically ports 80, 443, or 8080) is exposed to untrusted networks. Review firewall rules and IIS bindings for the Core server.Affected if The management console is accessible from outside the trusted network boundary, allowing remote authenticated attackers to reach the vulnerable interface.
-
Confirm authentication methods enabledReview Ivanti Endpoint Manager security settings to see which user authentication methods are active (e.g., local accounts, Active Directory integration, LDAP). Check user account configurations in the core console.Affected if Any authenticated user account (including low-privilege accounts) can access the management console, as the SQL injection affects authenticated users.
The environment is affected if Ivanti Endpoint Manager version 2024 or any version prior to 2024 SU5 is installed and the management console is accessible to remote 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 · scoped2024
Upgrade Ivanti Endpoint Manager to version 2024 SU5 or later to patch the SQL injection vulnerability. Restrict network access to the management console to trusted users only as an interim control.
Ivanti Endpoint Manager 2024 SU5
- Contact Ivanti support or log into the Ivanti Customer Portal to obtain the 2024 SU5 update package
- Review the Ivanti Endpoint Manager 2024 SU5 release notes for any prerequisites
- Follow standard Ivanti upgrade procedures for Endpoint Manager (backup database, test in non-production environment, schedule maintenance window)
- Apply the 2024 SU5 update to all affected Endpoint Manager instances
- Verify the upgrade was successful and test that the application functions normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62384 — 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-62384 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