dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2024-13163

HIGH · 7.8 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 2022 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Deserialization of untrusted data in Ivanti EPM before the 2024 January-2025 Security Update and 2022 SU6 January-2025 Security Update allows a remote unauthenticated attacker to achieve remote code execution. Local user interaction is required.

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 confidence

Ivanti Endpoint Manager (EPM) contains a deserialization vulnerability in versions prior to the 2024 January-2025 Security Update and the 2022 SU6 January-2025 Security Update. An unauthenticated remote attacker can achieve remote code execution by deserializing untrusted data, though local user interaction is required as part of the attack chain.

MitigationApply the January-2025 Security Updates for Ivanti EPM (both the 2024 and 2022 SU6 tracks) to address the deserialization vulnerability.

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
Endpoint ManagerApplication
Affected:< 2022= 2022= 2024

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.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checks

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

  1. Identify Ivanti Endpoint Manager version
    Check the installed Ivanti EPM version through the console, registry, or about page in the administration interface
    Affected if The version shows 2022 (any build) or 2024 (any build)
  2. Confirm update installation status
    Check if the January-2025 Security Update has been applied by reviewing the installed patches or updates in the EPM console or system information
    Affected if The January-2025 Security Update is not listed as installed, or the version is still at the pre-update release level
  3. Verify core EPM services are exposed
    Determine if the EPM core server is directly accessible from the network (ports 8080, 443, or default IIS bindings)
    Affected if The EPM server is externally accessible without network segmentation, as the flaw can be exploited by unauthenticated remote attackers
  4. Assess user interaction requirement
    Review whether the EPM server has local users or allows remote session establishment that could be leveraged as part of the attack chain
    Affected if The server has active local users or allows remote authentication flows that could be combined with the deserialization flaw

You are affected if you are running Ivanti EPM version 2022 or 2024 and have not applied the January-2025 Security Updates, especially if the server is network-accessible.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2022 or later
Fixed in 2022
Interim mitigation

Apply the January-2025 Security Updates for Ivanti EPM (both the 2024 and 2022 SU6 tracks) to address the deserialization vulnerability.

Recommended fix Moderate confidence

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

  1. 1. Identify current Ivanti Endpoint Manager version by checking About or system information in the console
  2. 2. Navigate to Ivanti Support portal or forums.ivanti.com to locate the January-2025 Security Update
  3. 3. For Ivanti EPM 2024: Apply the 2024 January-2025 Security Update
  4. 4. For Ivanti EPM 2022: Apply the 2022 SU6 January-2025 Security Update
  5. 5. Verify the update was applied successfully by checking the version again
  6. 6. Test critical functionality to ensure the update did not break existing workflows
Caveat Review release notes for any configuration or compatibility changes before applying

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

Fix this in Endpoint Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13163 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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