dbcve.org
Manageengine Log360Application · Zohocorp

CVE-2021-40177

CRITICAL · 9.8 CVSS v3.1 Published 2021-08-29
Fix available
A fix is available. Upgrade to after 5.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Zoho ManageEngine Log360 before Build 5225 allows remote code execution via BCP file overwrite.

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 · moderate confidence

Zoho ManageEngine Log360 before Build 5225 contains a vulnerability that allows remote code execution through BCP (Bulk Copy Program) file overwrite. An attacker can overwrite files on the affected system, potentially leading to arbitrary code execution with the privileges of the affected service.

MitigationUpgrade Zoho ManageEngine Log360 to Build 5225 or later to remediate this vulnerability. Given the critical severity (CVSS 9.8), priority patching is strongly recommended.

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
Manageengine Log360Application
Affected:<= 5.1= 5.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Log360 installation
    Locate the ManageEngine Log360 installation directory on the system (typically under C:\ManageEngine\ or similar). Check for the presence of the Log360 application files.
    Affected if Log360 is not installed on the system.
  2. Identify installed version
    Access the Log360 admin console or the About section within the application to retrieve the exact build number and version (e.g., Build XXXX). This information is usually found in the Help > About menu or in version-related configuration files within the installation directory.
    Affected if The version displayed is 5.1 or earlier, or version 5.2, and the build number is below 5225.
  3. Confirm build number against threshold
    Compare your identified build number to 5225. If the build number is lower than 5225, the instance is vulnerable regardless of whether the exact version number matches the affected ranges.
    Affected if Build number is less than 5225.
  4. Check BCP configuration
    Review Log360 configuration settings related to database connectivity and BCP (Bulk Copy Program) functionality. The vulnerability exploits the BCP feature to overwrite files, so any configuration enabling database import/export via BCP is relevant.
    Affected if BCP-related database features are enabled or configured in Log360.

The environment is affected if Zoho ManageEngine Log360 is installed with version 5.1 or earlier, version 5.2, or any build number below 5225.

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 a release after 5.1
Interim mitigation

Upgrade Zoho ManageEngine Log360 to Build 5225 or later to remediate this vulnerability. Given the critical severity (CVSS 9.8), priority patching is strongly recommended.

Recommended fix High confidence

ManageEngine Log360 Build 5225 or later

  1. 1. Identify the current build version of ManageEngine Log360 by accessing the About section in the product interface
  2. 2. If the current build is before Build 5225 (versions 5.1, 5.2, or earlier), plan for an upgrade
  3. 3. Download the latest version of ManageEngine Log360 from the official vendor website (www.manageengine.com)
  4. 4. Review the upgrade documentation provided by ManageEngine
  5. 5. Perform a full backup of the current Log360 configuration and database
  6. 6. Execute the upgrade installer, following the on-screen prompts
  7. 7. After upgrade completion, verify the build number reflects Build 5225 or later
  8. 8. Test critical logging and alerting functions to ensure normal operation
Caveat Review release notes for any configuration changes between your current version and Build 5225; test in non-production environment first

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

Fix this in Manageengine Log360 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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