CVE-2024-34787
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 · uneditedPath traversal in Ivanti Endpoint Manager before 2024 November Security Update or 2022 SU6 November Security Update allows a local unauthenticated attacker to achieve code execution. 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 confidenceA path traversal vulnerability in Ivanti Endpoint Manager allows a local unauthenticated attacker to escape the intended directory boundaries and access or write files outside the expected path, leading to code execution. The attacker requires user interaction on the target system to trigger the vulnerability, likely through social engineering or tricking a local user into accessing a malicious path or file.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Ivanti Endpoint Manager is installedCheck the installed programs list in Windows Control Panel or use 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' to list installed softwareAffected if Ivanti Endpoint Manager appears in the installed software list with a version matching < 2022, 2022, or 2024
-
Identify the installed version numberRun 'dism /online /get-packages' or check the registry at HKLM\SOFTWARE\LANDesk\ManageHub\Setup for version information, or look for version details in the Ivanti Endpoint Manager console under Help > AboutAffected if The version returned is any release of 2022 or 2024, or any version lower than 2022
-
Verify the Core Server service is runningOpen Services.msc and check if the 'LANDesk Management Server' or 'Ivanti Endpoint Manager Core' service exists and is running, or use 'Get-Service | Where-Object {$_.DisplayName -like "*Ivanti*" -or $_.DisplayName -like "*LANDesk*"}'Affected if The service is present and running, indicating the vulnerable component is active
-
Check for suspicious file access patternsReview Windows Event Viewer logs under Security and Application logs for events containing unusual path traversal patterns such as '..\' or '..%2F' in file access attempts, particularly around the Ivanti installation directoryAffected if Logs show file access attempts containing path traversal sequences outside the expected installation directory
-
Inspect web component logs if exposedIf the Ivanti Endpoint Manager web console is accessible, review IIS logs in C:\inetpub\logs\LogFiles for unusual path traversal requests or abnormal file write operationsAffected if IIS or web logs contain requests with path traversal patterns targeting system directories outside the Ivanti install path
You are affected if Ivanti Endpoint Manager version 2022, 2024, or any version below 2022 is installed and running on your system, and there are indicators of path traversal attempts in logs or unusual file access patterns.
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 November Security Update for Ivanti Endpoint Manager (either the 2024 release or the 2022 SU6 release depending on your current version). Verify the current version and test the patch in a non-production environment before deploying organization-wide.
2024 November Security Update or 2022 SU6 November Security Update (depending on current version)
- Identify the current version of Ivanti Endpoint Manager by checking the server console or system information
- If running version 2024.x, upgrade to the 2024 November Security Update
- If running version 2022.x (including 2022 SU1-SU5), upgrade to 2022 SU6 November Security Update
- If running a version prior to 2022, upgrade directly to either the 2024 November Security Update or 2022 SU6 November Security Update
- After upgrade, verify the version by checking the Ivanti Endpoint Manager console or documentation to confirm the security update is applied
- Test that core functionality (patch deployment, software distribution) works correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34787 — 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-34787 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