CVE-2021-40177

9.8 CRITICAL

📋 TL;DR

This vulnerability in Zoho ManageEngine Log360 allows attackers to execute arbitrary code remotely by overwriting BCP files. It affects all Log360 installations before Build 5225, potentially compromising entire systems.

💻 Affected Systems

Products:
  • Zoho ManageEngine Log360
Versions: All versions before Build 5225
Operating Systems: Windows, Linux
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all Log360 deployments regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system takeover with administrative privileges, data exfiltration, ransomware deployment, and lateral movement across the network.

🟠

Likely Case

Remote code execution leading to data theft, installation of backdoors, and disruption of log management services.

🟢

If Mitigated

Limited impact if proper network segmentation and access controls prevent external access to vulnerable instances.

🌐 Internet-Facing: HIGH - CVSS 9.8 indicates critical severity for internet-facing instances with no authentication required.
🏢 Internal Only: HIGH - Even internal instances are vulnerable to authenticated or network-adjacent attackers.

🎯 Exploit Status

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

The vulnerability allows remote exploitation without authentication, making it highly attractive to attackers.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Build 5225 or later

Vendor Advisory: https://www.manageengine.com/log-management/readme.html#Build%205225

Restart Required: Yes

Instructions:

1. Download Log360 Build 5225 or later from ManageEngine website. 2. Backup current installation. 3. Run the installer to upgrade. 4. Restart the Log360 service.

🔧 Temporary Workarounds

Network Isolation

all

Restrict network access to Log360 instances using firewall rules

File System Permissions

all

Restrict write permissions to BCP file directories

🧯 If You Can't Patch

  • Immediately isolate vulnerable Log360 instances from internet and production networks
  • Implement strict network segmentation and monitor for suspicious file modification attempts

🔍 How to Verify

Check if Vulnerable:

Check Log360 version in web interface or installation directory. If version is below Build 5225, system is vulnerable.

Check Version:

Check web interface at http://<log360-server>:<port> or examine installation directory version files

Verify Fix Applied:

Confirm version shows Build 5225 or higher in Log360 interface and verify BCP file permissions are properly configured.

📡 Detection & Monitoring

Log Indicators:

  • Unexpected BCP file modifications
  • Unusual process execution from Log360 directories
  • Failed authentication attempts followed by file operations

Network Indicators:

  • Unusual outbound connections from Log360 server
  • Exploit kit traffic patterns
  • BCP file transfer attempts

SIEM Query:

source="Log360" AND (event="File Modification" OR event="Process Execution") AND (file_path="*.bcp" OR process_name="cmd.exe" OR process_name="powershell.exe")

🔗 References

📤 Share & Export