CVE-2020-13774

9.9 CRITICAL

📋 TL;DR

This vulnerability allows authenticated attackers to upload malicious ASPX files to Ivanti Endpoint Manager servers, leading to remote code execution. Attackers can gain full control of affected systems. This affects Ivanti Endpoint Manager 2019.1 and 2020.1 installations.

💻 Affected Systems

Products:
  • Ivanti Endpoint Manager
  • Ivanti Unified Endpoint Manager
Versions: 2019.1 and 2020.1
Operating Systems: Windows Server
Default Config Vulnerable: ⚠️ Yes
Notes: Requires authenticated access to the web interface. The vulnerable component is EditLaunchPadDialog.aspx.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full server compromise leading to domain takeover, data exfiltration, and lateral movement across the network.

🟠

Likely Case

Attacker gains persistent access to the server, installs backdoors, and steals sensitive endpoint management data.

🟢

If Mitigated

Attack is detected and blocked before successful exploitation, or server is isolated to prevent lateral movement.

🌐 Internet-Facing: HIGH - If the management interface is exposed to the internet, attackers can directly exploit it.
🏢 Internal Only: HIGH - Even internally, authenticated users or compromised accounts can exploit this vulnerability.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: CONFIRMED
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation is straightforward once authenticated. The vulnerability is in file upload functionality with insufficient validation.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2020.2 and later

Vendor Advisory: https://forums.ivanti.com/s/article/Security-Advisory-EPM-2020-2-and-older

Restart Required: Yes

Instructions:

1. Download and install Ivanti Endpoint Manager 2020.2 or later. 2. Apply all security patches. 3. Restart the Ivanti Endpoint Manager service. 4. Verify the patch is applied successfully.

🔧 Temporary Workarounds

Restrict file upload extensions

windows

Configure web application firewall or server rules to block ASPX file uploads to the vulnerable endpoint.

# Example IIS URL Rewrite rule to block .aspx uploads to EditLaunchPadDialog.aspx
<rule name="Block ASPX Upload" stopProcessing="true">
  <match url="EditLaunchPadDialog\.aspx" />
  <conditions>
    <add input="{QUERY_STRING}" pattern=".*\.aspx" />
  </conditions>
  <action type="CustomResponse" statusCode="403" statusReason="Forbidden" />
</rule>

Remove vulnerable file

windows

Temporarily remove or rename the vulnerable EditLaunchPadDialog.aspx file.

rename "C:\Program Files\LANDesk\ManagementSuite\wwwroot\EditLaunchPadDialog.aspx" "EditLaunchPadDialog.aspx.bak"
# Or move to backup location
move "C:\Program Files\LANDesk\ManagementSuite\wwwroot\EditLaunchPadDialog.aspx" "C:\backup\"

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate Ivanti Endpoint Manager servers from critical systems.
  • Enable detailed logging and monitoring for file upload activities to the vulnerable endpoint.

🔍 How to Verify

Check if Vulnerable:

Check if EditLaunchPadDialog.aspx exists in the web directory and test if ASPX files can be uploaded.

Check Version:

Check the Ivanti Endpoint Manager console or review the installation directory for version information.

Verify Fix Applied:

Verify the Ivanti Endpoint Manager version is 2020.2 or later and test that ASPX file uploads are properly rejected.

📡 Detection & Monitoring

Log Indicators:

  • ASPX file uploads to EditLaunchPadDialog.aspx
  • Unusual file creation in temporary directories
  • Failed file validation attempts

Network Indicators:

  • HTTP POST requests to EditLaunchPadDialog.aspx with file uploads
  • Unusual outbound connections from the Ivanti server

SIEM Query:

source="iis_logs" AND uri="*EditLaunchPadDialog.aspx*" AND (method="POST" OR file_extension=".aspx")

🔗 References

📤 Share & Export