CVE-2024-13165
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 confidenceIvanti Endpoint Manager (EPM) contains an out-of-bounds write vulnerability in versions prior to the 2024 January-2025 Security Update and 2022 SU6 January-2025 Security Update. A remote unauthenticated attacker can exploit this memory corruption flaw to cause 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.
-
Confirm Ivanti Endpoint Manager installationLocate the Ivanti Endpoint Manager service or application on the system, typically found in Program Files or as a Windows service named 'Ivanti Endpoint Manager' or 'LANDesk Management'Affected if The software is not present on the system
-
Identify the installed EPM versionCheck the installed version through the Ivanti Endpoint Manager console, Windows Add/Remove Programs, or by querying the registry under HKLM\SOFTWARE\LANDesk\ManageLite\ or similar Ivanti registry keysAffected if The version cannot be determined or is earlier than the January-2025 Security Update
-
Compare version against vulnerable releasesReview the detected version number against the affected ranges: versions before 2024, version 2022, and version 2024 releases prior to the January-2025 updateAffected if The installed version falls within < 2022, = 2022, or = 2024 and has not received the January-2025 Security Update
-
Verify if the January-2025 update is appliedCheck the installed patches or update history within the Ivanti Endpoint Manager console or by reviewing installed updates for a January-2025 dated security updateAffected if The January-2025 Security Update is not listed as installed
A system is affected if Ivanti Endpoint Manager is installed with version 2022, version 2024, or any version prior to 2024, and the January-2025 Security Update has not been 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 and the January-2025 Security Update for EPM 2022 SU6 to address this vulnerability.
2024 January-2025 Security Update (for 2024) or 2022 SU6 January-2025 Security Update (for 2022)
- Identify the current installed version of Ivanti Endpoint Manager (EPM)
- For EPM 2024: Apply the 2024 January-2025 Security Update
- For EPM 2022: Apply the 2022 SU6 January-2025 Security Update
- Verify the update was successfully applied and the service is running
- Confirm the vulnerability is remediated by reviewing the installed patch level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13165 — 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-13165 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