dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2020-13774

CRITICAL · 9.9 CVSS v3.1 Published 2020-11-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 unrestricted file-upload issue in EditLaunchPadDialog.aspx in Ivanti Endpoint Manager 2019.1 and 2020.1 allows an authenticated attacker to gain remote code execution by uploading a malicious aspx file. The issue is caused by insufficient file extension validation and insecure file operations on the uploaded image, which upon failure will leave the temporarily created files in an accessible location on the server.

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

Unrestricted file upload vulnerability in EditLaunchPadDialog.aspx in Ivanti Endpoint Manager 2019.1 and 2020.1 allows authenticated attackers to upload malicious ASPX files due to insufficient file extension validation and insecure temporary file handling. The insecure file operations leave temporary files in an accessible location upon upload failure, enabling remote code execution.

MitigationApply vendor patches for Ivanti Endpoint Manager. Implement strict allowlist-based file extension validation, store uploads outside the web root in non-executable directories, and ensure proper cleanup of temporary files.

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:= 2019.1= 2020.1

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 installed Ivanti Endpoint Manager version
    Check the product version through the Control Panel, registry, or the built-in About page in the Ivanti console. Common paths: HKEY_LOCAL_MACHINE\SOFTWARE\LANDesk\LDMain\Version or examine the installation directory for version.txt
    Affected if The installed version matches exactly 2019.1 or 2020.1
  2. Verify EditLaunchPadDialog.aspx is accessible
    Navigate to the URL path /Connector/EditLaunchPadDialog.aspx on the server's web interface, or check if the file exists in the web root directory under the Connector or corresponding application folder
    Affected if The EditLaunchPadDialog.aspx file exists and responds to HTTP requests
  3. Confirm authentication access to the upload feature
    Check user account permissions in Ivanti Endpoint Manager console. Determine if the testing account has access to the LaunchPad or customization features that invoke EditLaunchPadDialog.aspx
    Affected if The account used has privileges to access the LaunchPad customization or file upload interface
  4. Inspect temporary file handling configuration
    Examine the web.config and application settings for upload temp directory paths. Check the IIS site configuration for the temporary upload folder location and its NTFS permissions
    Affected if Temporary files are stored in a location accessible via web (within web root) or lack proper access restrictions

You are affected if you run Ivanti Endpoint Manager version 2019.1 or 2020.1, the EditLaunchPadDialog.aspx upload page is accessible, and authenticated users can access the file upload functionality with insecure temporary file storage in place.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for Ivanti Endpoint Manager. Implement strict allowlist-based file extension validation, store uploads outside the web root in non-executable directories, and ensure proper cleanup of temporary files.

Recommended fix Moderate confidence

Latest stable Ivanti Endpoint Manager version (contact Ivanti support for specific fixed version)

  1. 1. Identify the current Ivanti Endpoint Manager version in your environment (2019.1 or 2020.1)
  2. 2. Contact Ivanti support or consult the official Ivanti security advisory for this CVE to obtain the specific patch or fixed version
  3. 3. Plan an upgrade to the latest stable release of Ivanti Endpoint Manager that addresses CVE-2020-13774
  4. 4. Before applying in production, test the upgrade in a staging environment to verify functionality
  5. 5. After upgrade, verify the EditLaunchPadDialog.aspx upload functionality is secured with proper file extension validation
  6. 6. Ensure the server is patched with latest security updates and follow principle of least privilege for user accounts
Caveat Review Ivanti upgrade documentation for any configuration or compatibility changes between 2019.1/2020.1 and the target version

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

Fix this in Endpoint Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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