CVE-2024-29822
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 · moderate confidenceSQL injection vulnerability in Ivanti EPM Core server allows unauthenticated attackers within the same network to execute arbitrary code due to unsanitized SQL input.
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.
-
Confirm Ivanti Endpoint Manager installationLocate the Ivanti Endpoint Manager (EPM) Core server installation on the system. Check for the 'Ivanti Endpoint Manager Core' service or the EPM installation directory.Affected if The product is installed and is Ivanti Endpoint Manager Core server.
-
Identify installed EPM versionUse the product's built-in version information mechanism (such as the About dialog in the console, or the version reported by the Core server service) to determine the exact installed version number.Affected if The installed version is 2022 or any version prior to 2022 (any version < 2022).
-
Verify Core server component is presentConfirm the Core server component is installed and running. This is the component vulnerable to the SQL injection flaw.Affected if The Core server component is present and operational on the target system.
-
Assess network accessibility to Core serverDetermine if the Core server is reachable over the network by untrusted endpoints. Check firewall rules and network exposure settings that govern access to the Core server service port.Affected if The Core server is accessible over the network to endpoints outside the trusted management scope.
A system is affected if it runs Ivanti Endpoint Manager Core server version 2022 or any version prior to 2022, and the Core server is network-accessible to untrusted endpoints.
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 vendor patch for CVE-2024-29822 to Ivanti EPM 2022 SU5 or later; until patched, restrict network access to the Core server to trusted endpoints only.
Ivanti EPM 2022 SU6 or later / Latest available EPM version
- Obtain the latest Ivanti Endpoint Manager 2022 Service Update (SU6 or later) or the most recent EPM version from the official Ivanti portal
- Review the Ivanti EPM upgrade documentation for pre-upgrade requirements
- Backup the current Ivanti EPM database and configuration
- Ensure the Core server meets the system requirements for the target version
- Apply the upgrade following Ivanti's standard upgrade procedures
- Verify the upgrade was successful by checking the Core server services
- Validate that the SQL injection vulnerability is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29822 — 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-29822 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