CVE-2024-13170
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 allows remote unauthenticated attackers to write data beyond allocated memory boundaries, leading to a denial of service condition. The vulnerability exists in versions prior to the January-2025 Security Updates.
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.
-
Confirm Ivanti Endpoint Manager is installedCheck installed programs list or running services for 'Ivanti Endpoint Manager' or 'EPM' entries. On Windows, review Add/Remove Programs or the Windows Services list.Affected if The software is present on the system
-
Determine the installed version of Ivanti Endpoint ManagerCheck the application's About page, the installed programs list version column, or the service executable version information. Look for version strings such as 2022.x, 2024.x, or earlier.Affected if The displayed version matches < 2022, = 2022, or = 2024 (any 2022 or 2024 release)
-
Verify the version is prior to January-2025 updatesCross-reference your installed version with release notes or check for recent security update installations labeled 'January 2025' or later.Affected if No January-2025 or later security update has been applied
-
Assess network exposure of the EPM serviceReview firewall rules and network configurations to determine if the EPM web interface or API endpoints are accessible from untrusted networks without authentication.Affected if The EPM service is reachable from unauthenticated remote attackers on the network
The environment is affected if Ivanti Endpoint Manager is installed with a version of 2022 or 2024 (or any version prior to 2022) and the service is network-accessible to unauthenticated users without having applied the January-2025 security updates.
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 (either the 2024 version or 2022 SU6 version depending on your deployment). If immediate patching is not possible, consider network segmentation to limit exposure to unauthenticated attackers.
2022 SU6 January-2025 Security Update (for v2022) or 2024 January-2025 Security Update (for v2024)
- Identify your current Ivanti Endpoint Manager version (2022 or 2024)
- For Ivanti EPM 2022: Upgrade to version 2022 SU6 (January-2025 Security Update)
- For Ivanti EPM 2024: Upgrade to the 2024 January-2025 Security Update
- Verify the upgrade was successful and the service is running normally
- Test that core EPM functions (patch deployment, software distribution, asset discovery) are operating as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.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,440.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13170 — 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-13170 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