dbcve.org
Manageengine Endpoint CentralApplication · Zohocorp

CVE-2024-10203

HIGH · 7.8 CVSS v3.1 Published 2024-11-07
Fix available
A fix is available. Upgrade to after 11.3.2428.09 or later.
See remediation →
80/100
Remediation priority · High
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
Zohocorp ManageEngine EndPoint Central versions 11.3.2416.21 and below, 11.3.2428.9 and below are vulnerable to Arbitrary File Deletion in the agent installed machines.

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

Zohocorp ManageEngine EndPoint Central versions 11.3.2416.21 and below and 11.3.2428.9 and below contain an arbitrary file deletion vulnerability in the agent component installed on managed machines. An attacker with low privileges on the agent-equipped endpoint could potentially delete arbitrary files on the system, leading to denial of service or data destruction.

MitigationUpgrade ManageEngine EndPoint Central to a version above 11.3.2416.21 and 11.3.2428.9 respectively, or apply the vendor's latest security patch. Verify all agent installations across the environment are updated to the patched version.

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 Endpoint CentralApplication
Affected:<= 11.3.2416.21>= 11.3.2428.01, <= 11.3.2428.09

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Locate Endpoint Central agent installation
    Search for ManageEngine Endpoint Central agent installation directories. Common locations include: C:\Program Files\ManageEngine\EndpointCentral\ or C:\Program Files (x86)\ManageEngine\EndpointCentral\ on Windows; /opt/ManageEngine/EndpointCentral/ or /home/<user>/ManageEngine/EndpointCentral/ on Linux. Also check for service entries using 'sc query' on Windows or 'ls -la /etc/init.d/' and 'systemctl list-units' on Linux for the 'EndpointCentral' or 'DesktopCentral' agent service.
    Affected if Endpoint Central agent is found installed on the system
  2. Identify agent version
    On Windows, check the version of the agent executable (typically EndpointCentral.exe or a related DLL) by right-clicking the file, selecting Properties, and viewing the Details tab. On Linux, run: find /opt/ManageEngine -name 'version.txt' 2>/dev/null or check for version information in the agent's bin directory. Alternatively, check the agent's service properties via 'sc qc EndpointCentral' on Windows.
    Affected if Version cannot be determined or matches the affected ranges (<=11.3.2416.21 or >=11.3.2428.01 through <=11.3.2428.09)
  3. Verify agent service is active
    On Windows, run 'sc query EndpointCentral' or check Task Manager for EndpointCentral.exe processes. On Linux, run 'systemctl status endpointcentral' or 'ps -ef | grep -i endpointcentral' to confirm the agent service is running.
    Affected if Agent service is running on the system (the vulnerability affects the active agent component)
  4. Check agent user privileges
    Review the service logon account for the Endpoint Central agent service. On Windows, run 'sc qc EndpointCentral' and note the SERVICE_START_NAME. On Linux, check the agent's run-user via 'grep -r "run_as_user\|run_as_group" /opt/ManageEngine/EndpointCentral/' or inspect the init script. The vulnerability is exploitable by low-privilege users on the endpoint.
    Affected if Agent runs with elevated privileges but accepts commands from low-privilege users (the vulnerable configuration)

A system is affected if the Endpoint Central agent is installed and its version falls within 11.3.2416.21 and below OR between 11.3.2428.01 and 11.3.2428.09, with the agent service actively running.

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.

From vendor data
Upgrade available Upgrade to a release after 11.3.2428.09
Interim mitigation

Upgrade ManageEngine EndPoint Central to a version above 11.3.2416.21 and 11.3.2428.9 respectively, or apply the vendor's latest security patch. Verify all agent installations across the environment are updated to the patched version.

Fix this in Manageengine Endpoint Central Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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