Endpoint ManagerApplication · Ivanti

CVE-2024-13167

HIGH · 7.5 CVSS v3.1 Published 2025-01-14

Fix available

A fix is available. Upgrade to 2022 or later.

See remediation →

84/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

An 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

dbcve analysis · moderate confidence

An 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. The vulnerability affects versions prior to the January-2025 security updates for both the 2024 release and 2022 SU6 release.

MitigationApply the January-2025 Security Update for Ivanti EPM 2024 and the January-2025 Security Update for Ivanti EPM 2022 SU6 to address this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Endpoint ManagerApplication

Affected:< 2022= 2022= 2024

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Confirm Ivanti Endpoint Manager is installed

Check for the presence of Ivanti Endpoint Manager services or software on the system, typically via the Windows Add/Remove Programs list or by searching for Ivanti EPM-related services in the system service list.

Affected if Ivanti Endpoint Manager is found to be installed on the system
Identify the installed EPM version

Locate the EPM version information through the Windows registry at HKLM\SOFTWARE\Ivanti\EndpointManager, or check the about/version section within the EPM admin console if accessible, or use the Ivanti EPM diagnostic tool if available.

Affected if The version displayed is 2024 (any build) or 2022 (any build), or any version released prior to January 2025
Determine if January-2025 security updates have been applied

Check the installed patches or updates on the EPM server for the January-2025 security update specific to Ivanti EPM 2024 or EPM 2022 SU6, which can be verified through Windows Update history or the Ivanti knowledge base.

Affected if The January-2025 security update for Ivanti EPM is NOT listed among installed updates

A system is affected if Ivanti Endpoint Manager 2024 or 2022 is installed without the January-2025 security updates applied, as this out-of-bounds write vulnerability can be exploited remotely by unauthenticated attackers to cause denial of service.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 2022 or later

Fixed in 2022

Interim mitigation

Apply the January-2025 Security Update for Ivanti EPM 2024 and the January-2025 Security Update for Ivanti EPM 2022 SU6 to address this vulnerability.

Recommended fix Moderate confidence

2024 January-2025 Security Update or 2022 SU6 January-2025 Security Update (depending on baseline version)

Identify the current version of Ivanti Endpoint Manager (EPM) in use
If running version 2024.x: Apply the January-2025 Security Update for the 2024 release
If running version 2022.x: Apply the SU6 January-2025 Security Update for the 2022 release
If running any version before 2022: Plan migration to a supported version (2022 SU6 or 2024 with latest updates)
After applying the update, verify the version reflects the patched release

Caveat Standard testing recommended before deploying security updates in production environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Endpoint Manager Scoped from the published advisory

Consultation3.0 h
Implementation4.0 h
Testing3.0 h
Review / QA2.0 h

12.0 hours of engineering $2,130

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2024-13167 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

forums.ivanti.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-13167 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-13167?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsUpgrade to 2022 or later

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 2.6%

Affects: Endpoint Manager

Remediation

A high-priority fix

Fix this in Endpoint Manager 12 hrs · Moderate

Typical engagement from $2,130

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2024-13167 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

CVSS 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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References