CVE-2024-13164
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 uninitialized resource in Ivanti EPM before the 2024 January-2025 Security Update and 2022 SU6 January-2025 Security Update allows a local authenticated attacker to escalate their privileges.
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 uninitialized resource vulnerability in versions prior to the January-2025 Security Update (and 2022 SU6 January-2025 Security Update). A locally authenticated attacker can exploit this flaw to escalate their privileges, likely gaining administrative or SYSTEM-level access on the affected endpoint.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 installation directory (commonly under Program Files\Ivanti or Program Files\LANDesk) and verify the core application files exist, such as the main EPM executable or service binary.Affected if The product is not installed or only partially present.
-
Identify installed EPM versionCheck the version of the primary EPM executable or service binary. This can typically be done via file properties in Windows Explorer, or by running 'wmic product where "name like '%Ivanti%'" get version' if the product is registered as a Windows installer, or by querying the service information via 'sc query' for the EPM service.Affected if The version cannot be determined or the product is not registered as an installed application.
-
Compare version against affected rangesEvaluate the identified version against the vulnerable ranges: any version prior to 2022, version 2022 prior to the SU6 January-2025 update, or version 2024 prior to the January-2025 update. Versions 2022 SU6 with the January-2025 patch and 2025 and later are not affected.Affected if The installed version falls within < 2022, = 2022 (pre-SU6 Jan-2025), or = 2024 (pre-Jan-2025 update).
-
Verify EPM service is runningConfirm that the Ivanti Endpoint Manager service is currently running on the system. Use 'sc query' or the Services console (services.msc) to check the status of the EPM-related service (commonly named 'LANDesk Management Service' or 'Ivanti Endpoint Manager Service').Affected if The service is not running; exploitation requires the service to be active as it is a local privilege escalation from an authenticated user context.
-
Check for recent security updatesReview installed Windows updates or Ivanti-specific patches. Look for the January-2025 Security Update or the 2022 SU6 January-2025 Security Update depending on the branch. This can be checked via 'Get-HotFix' or by reviewing the program's update history if accessible.Affected if The January-2025 security update has not been applied to the installed version.
A system is affected if Ivanti Endpoint Manager is installed with a version in the < 2022, = 2022 (pre-SU6 Jan-2025), or = 2024 (pre-Jan-2025) range and the EPM service is running, allowing a locally authenticated attacker to escalate privileges.
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 January-2025 Security Update (or 2022 SU6 January-2025 Security Update for older branches) to all affected Ivanti EPM installations. Prioritize systems with direct user access where untrusted local accounts may exist.
Ivanti EPM 2024 with January-2025 Security Update, or Ivanti EPM 2022 SU6 with January-2025 Security Update
- Navigate to the Ivanti Endpoint Manager admin console
- Locate the System Updates or Patch Management section
- Apply the 'January-2025 Security Update' for Ivanti EPM 2024 (or latest available 2024.x version)
- Apply the 'SU6 January-2025 Security Update' for Ivanti EPM 2022 (or latest available 2022 SUx version)
- Verify the patch was applied successfully by checking the software version/build number
- Restart the Ivanti Endpoint Manager services if required by the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13164 — 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-13164 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