CVE-2024-13168
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 · high confidenceAn out-of-bounds write vulnerability in Ivanti Endpoint Manager (EPM) allows remote unauthenticated attackers to write data beyond allocated buffer boundaries. This occurs in unpatched versions before the January-2025 Security Update (both the 2024 release track and 2022 SU6 release track). Successful exploitation results in denial of service conditions.
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.
-
Identify installed Ivanti Endpoint Manager versionLocate the EPM version through the administration console (typically under Help > About or Server > Configuration), or query the core server via command line if availableAffected if The installed version is 2022 or 2024 (or any version before 2022)
-
Confirm the January-2025 Security Update statusCheck the installed updates or patch level on the EPM core server. This is typically visible in the console under Updates/Patches section, or via the server's update historyAffected if The January-2025 Security Update has NOT been applied to the installation
-
Determine the correct release trackIdentify whether the installation follows the 2024 release track or the 2022 SU6 release track, based on the base version installedAffected if The version matches the 2022 or 2024 release line and remains on the pre-January-2025 patch level
If the Ivanti EPM version is 2022 or 2024 (or earlier) AND the January-2025 Security Update has not been applied, the environment is affected by this vulnerability.
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 track or 2022 SU6 track depending on your version). Organizations should test the patch in a non-production environment before rolling out enterprise-wide due to the critical nature of endpoint management infrastructure.
2022 SU6 January-2025 Security Update or 2024 January-2025 Security Update (depending on your base version)
- Identify your current Ivanti Endpoint Manager version (2022 or 2024)
- For Ivanti EPM 2022: Apply the 2022 SU6 January-2025 Security Update
- For Ivanti EPM 2024: Apply the 2024 January-2025 Security Update
- Verify the patch was applied successfully by checking the software version or build number
- Test that the Ivanti EPM services start and function normally after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing12.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 $7,104.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13168 — 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-13168 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