CVE-2024-29824
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 vulnerability in Core server of Ivanti EPM 2022 SU5 and prior allows an unauthenticated attacker within the same network to execute arbitrary code.
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 the Core server component of Ivanti Endpoint Manager (EPM) 2022 SU5 and prior allows an unauthenticated attacker with network access to the same network as the Core server to execute arbitrary code through unspecified injection vectors.
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= 2022CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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 if Ivanti Endpoint Manager is installedCheck for Ivanti Endpoint Manager installation by looking for the EPM installation directory (commonly at C:\Program Files\Ivanti\EndpointManager or similar), or check Windows Services for 'Ivanti Endpoint Manager' or 'Core' service entries.Affected if The software is not found or no EPM-related services exist, the system is not affected.
-
Determine the installed EPM versionOpen Windows Registry and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Ivanti\EndpointManager or check the version information in the Core server executable. Look for a version string that indicates the 2022 release and Service Update level (SU1 through SU5).Affected if The installed version is 2022 with any Service Update 5 or lower, or any version of 2022 prior to SU5, indicating the system is affected.
-
Verify the Core server component is present and runningCheck Windows Services for the 'Ivanti Core' or 'Endpoint Manager Core' service, or examine the Core server process in Task Manager. The vulnerability affects the Core component specifically.Affected if The Core server component is installed and running, the system could be affected if the version is vulnerable.
-
Check network exposure of the Core serverIdentify the port the Core server listens on (typically port 443 or configured port), then use netstat or a network scanner to determine if the Core server port is accessible from untrusted networks. Review firewall rules allowing inbound access to the EPM server.Affected if The Core server port is exposed to untrusted network segments or the internet, an unauthenticated attacker could reach the vulnerable component.
The environment is affected if Ivanti Endpoint Manager 2022 SU5 or any prior version is installed, the Core server component is present, and the Core server port is accessible from a network where untrusted attackers can send SQL queries.
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 Ivanti EPM 2022 SU6 or later patches immediately; restrict network access to the Core server to trusted internal systems until the patch is deployed.
Ivanti EPM 2022 SU6 or later / latest available release
- Obtain the latest Ivanti Endpoint Manager version from the official Ivanti download portal or contact Ivanti Customer Support
- Review Ivanti EPM 2022 release notes and security advisories for version 2022 SU6 or later which contains the fix for CVE-2024-29824
- Backup the current Ivanti EPM database and configuration before proceeding with upgrade
- Stop all Ivanti services on the Core server
- Install the updated version (2022 SU6 or newer, or migrate to the latest available release)
- Start Ivanti services and verify the Core server is operational
- Validate that the SQL Injection vulnerability is remediated by confirming the patch is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.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,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29824 — 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-29824 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