CVE-2024-32846
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 unspecified SQL injection in Ivanti EPM before 2022 SU6, or the 2024 September update allows a remote authenticated attacker with admin privileges to achieve remote code execution.
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 confidenceIvanti Endpoint Manager (EPM) contains an SQL injection vulnerability in versions prior to 2022 SU6 or the September 2024 update. A remote attacker with administrative privileges can inject malicious SQL queries, potentially executing arbitrary code on the underlying system.
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
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 installationLocate the EPM installation directory or check Add/Remove Programs for 'Ivanti Endpoint Manager'. The version is typically displayed in the product's About dialog or can be found in registry at HKEY_LOCAL_MACHINE\SOFTWARE\LANDesk\Manage\Setup or through the Core Server console.Affected if The installed version is prior to 2022 SU6 or the September 2024 update, or matches version 2022 or 2024 exactly.
-
Confirm the Core Server component versionOn the Ivanti EPM Core server, open the Core Server console and navigate to Help > About, or check the version.xml file in the Core Server installation directory (typically in C:\Program Files\LANDesk\ManagementSuite or similar).Affected if The displayed version falls outside the safe range (not 2022 SU6 or later, not September 2024 update).
-
Verify administrative access surfaceCheck if the EPM admin console (typically port 443 or 8080) is exposed to untrusted networks. Review user accounts in the EPM console under Administration > Users to identify accounts with Administrative privileges.Affected if The administrative console is accessible from untrusted networks or there are administrative accounts that could be leveraged for exploitation.
-
Review SQL query loggingEnable and inspect EPM SQL logging if available, or check database audit logs for the EPM database (commonly LANDESK or LDMAIN) for unusual or malicious SQL patterns.Affected if Suspicious SQL injection patterns are found in logs, especially from administrative sessions.
A user is affected if their Ivanti EPM installation version is prior to 2022 SU6 or the September 2024 update AND the administrative interface is accessible to an attacker.
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
Apply the vendor-supplied patch: upgrade to Ivanti EPM 2022 SU6 or later, or apply the September 2024 update. Alternatively, restrict administrative access to trusted personnel and monitor for suspicious SQL activity.
Ivanti EPM 2022 SU6 or later; or the 2024 September update
- 1. Identify the current installed version of Ivanti Endpoint Manager (EPM) by checking the console or system information.
- 2. If running a version before 2022 Service Update 6 (SU6), plan to upgrade to 2022 SU6 or later.
- 3. If running the 2024 branch, upgrade to the 2024 September update or later.
- 4. Download the appropriate update from the Ivanti Customer Portal (account.ivanti.com) or through the standard update distribution channel.
- 5. Apply the update during a planned maintenance window following Ivanti's standard upgrade procedures.
- 6. Verify the update was successful by checking the version number post-upgrade.
- 7. Confirm the SQL injection vulnerability is remediated by reviewing release notes for the fixed version.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32846 — 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-2024-32846 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