dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2023-38344

MEDIUM · 6.5 CVSS v3.1 Published 2023-09-21
Fix available
A fix is available. Upgrade to 2022 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
An issue was discovered in Ivanti Endpoint Manager before 2022 SU4. A file disclosure vulnerability exists in the GetFileContents SOAP action exposed via /landesk/managementsuite/core/core.secure/OsdScript.asmx. The application does not sufficiently restrict user-supplied paths, allowing for an authenticated attacker to read arbitrary files from a remote system, including the private key used to authenticate to agents for remote access.

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

A path traversal vulnerability in the GetFileContents SOAP action of Ivanti Endpoint Manager's OsdScript.asmx endpoint allows an authenticated attacker to read arbitrary files from the server by manipulating user-supplied paths, potentially exposing sensitive files like private keys used for remote agent authentication.

MitigationUpgrade to Ivanti Endpoint Manager 2022 SU4 or later. Additionally, restrict access to the /landesk/managementsuite/core/core.secure/OsdScript.asmx endpoint to only necessary authenticated users and implement proper input validation on the GetFileContents action.

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

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 version of Ivanti Endpoint Manager in the registry or through the product's About/Version information. Compare against the affected ranges: versions < 2022 and version 2022.
    Affected if The installed version is 2022 or any version prior to 2022.
  2. Locate the OsdScript.asmx endpoint
    Search for the OsdScript.asmx file in the Ivanti installation directory, typically under /landesk/managementsuite/core/core.secure/ or check if this endpoint is accessible via HTTP/HTTPS on the server.
    Affected if The OsdScript.asmx file exists and is present in the expected location or responds to requests.
  3. Verify if the GetFileContents SOAP action is exposed
    Examine the WSDL or endpoint configuration for OsdScript.asmx to confirm the GetFileContents method is available and enabled.
    Affected if The GetFileContents action is present and operational in the SOAP service.
  4. Check if authentication is required for the endpoint
    Review the authentication configuration for the OsdScript.asmx endpoint in IIS or the application server configuration to determine whether anonymous access is permitted.
    Affected if The endpoint allows unauthenticated access or uses weak authentication that could be bypassed.

You are affected if Ivanti Endpoint Manager version 2022 or any prior version is installed and the OsdScript.asmx endpoint with the GetFileContents SOAP action is accessible, regardless of authentication status as the CVE states it affects authenticated attackers.

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

Upgrade to Ivanti Endpoint Manager 2022 SU4 or later. Additionally, restrict access to the /landesk/managementsuite/core/core.secure/OsdScript.asmx endpoint to only necessary authenticated users and implement proper input validation on the GetFileContents action.

Recommended fix High confidence

Ivanti Endpoint Manager 2022 Service Update 4 (SU4)

  1. Download Ivanti Endpoint Manager 2022 Service Update 4 (SU4) from the official Ivanti download portal or through your authorized licensing channel
  2. Review the Ivanti Endpoint Manager 2022 SU4 release notes and upgrade prerequisites documentation
  3. Backup the current Endpoint Manager database and configuration
  4. Ensure all system prerequisites are met for the upgrade (including OS version, SQL Server requirements, and disk space)
  5. Stop all Endpoint Manager services before initiating the upgrade
  6. Run the Endpoint Manager 2022 SU4 installer with appropriate administrative privileges
  7. Follow the on-screen installation wizard, selecting the upgrade option
  8. After installation completes, verify all services start successfully
Caveat Review upgrade documentation for potential impacts to custom scripts, third-party integrations, or legacy agent compatibility; test in non-production environment first

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

Fix this in Endpoint Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,260
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-38344 — 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-2023-38344 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