CVE-2024-13166
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 out-of-bounds write in Ivanti EPM before the 2024 January-2025 Security Update and 2022 SU6 January-2025 Security Update allows a remote unauthenticated attacker to cause a denial of service.
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 confidenceAn out-of-bounds write vulnerability in Ivanti Endpoint Manager (EPM) allows a remote unauthenticated attacker to write data beyond allocated memory boundaries, causing a denial of service condition.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Locate Ivanti Endpoint Manager installationIdentify the server or workstation where Ivanti Endpoint Manager is installed. Common installation paths include C:\Program Files\Ivanti\Endpoint Manager\ or C:\Program Files (x86)\Ivanti\Endpoint Manager\ on Windows systems.Affected if Ivanti Endpoint Manager software is present on the system
-
Determine installed version of Ivanti EPMCheck the product version by opening the Ivanti Endpoint Manager console and navigating to Help > About, or locate the version information in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Ivanti\EndpointManager\ or in the installation directory's version file.Affected if The displayed version is 2022, 2024, or any version prior to 2022 (e.g., 2021, 2020, older)
-
Check for installed updates or service packsIf the version shows as 2022 or 2024, verify whether Service Pack 6 (SU6) for version 2022 or the January-2025 Security Update for version 2024 has been applied by reviewing the update history in the Ivanti Endpoint Manager console or Windows Update history.Affected if No security updates have been applied to version 2022 or 2024, leaving the installation at the base release version
-
Verify if the core server service is accessibleConfirm that the Ivanti Endpoint Manager core service (often named 'Ivanti Endpoint Manager Server' or 'LDMS') is running and listening on its default ports (default HTTP port 80 or HTTPS port 443).Affected if The service is running and accessible to network attackers without authentication
You are affected if Ivanti Endpoint Manager is installed at version 2022, 2024, or any version before 2022 without the January-2025 security update or SU6 applied.
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 for Ivanti EPM 2024 or the January-2025 Security Update for Ivanti EPM 2022 SU6 to remediate this vulnerability.
2024 January-2025 Security Update or 2022 SU6 January-2025 Security Update (depending on your current version)
- Obtain the appropriate January-2025 Security Update for your current Ivanti EPM version from the Ivanti download portal or official support channels
- Backup your current Ivanti EPM database and configuration
- Review Ivanti EPM upgrade documentation for your specific version
- Apply the 2024 January-2025 Security Update if running version 2024
- Apply the 2022 SU6 January-2025 Security Update if running version 2022
- Verify the update was applied successfully through the EPM console
- Confirm the vulnerability is resolved by checking the installed version/build number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13166 — 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-13166 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