dbcve.org
Manageengine Desktop CentralApplication · Zohocorp

CVE-2017-16924

CRITICAL · 9.8 CVSS v3.0 Published 2018-02-19
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 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
Remote Information Disclosure and Escalation of Privileges in ManageEngine Desktop Central MSP 10.0.137 allows attackers to download unencrypted XML files containing all data for configuration policies via a predictable /client-data/<client_id>/collections/##/usermgmt.xml URL, as demonstrated by passwords and Wi-Fi keys. This is fixed in build 100157.

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

ManageEngine Desktop Central MSP 10.0.137 contains an information disclosure vulnerability where unauthenticated attackers can access sensitive XML configuration files (usermgmt.xml) via a predictable URL path /client-data/<client_id>/collections/##/usermgmt.xml. These XML files contain plaintext passwords and Wi-Fi keys used in configuration policies.

MitigationUpgrade to ManageEngine Desktop Central MSP build 100157 or later to remediate this vulnerability. Additionally, review and restrict access to the /client-data/ directory and ensure sensitive configuration data is encrypted at rest.

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 Desktop CentralApplication
Affected:= 10.0.137

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.0/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. Confirm the installed version of ManageEngine Desktop Central MSP
    Access the ManageEngine Desktop Central MSP admin console, typically at https://<server>:8020/ or check the application startup logs/banner. Navigate to the 'About' or 'Server Details' section to view the build number.
    Affected if The installed version is exactly 10.0.137 (no other versions are listed as affected)
  2. Verify the /client-data/ endpoint is web-accessible
    From a system with network access to the Desktop Central server, attempt to reach http://<server>:<port>/client-data/ via a web browser or curl command.
    Affected if The server returns any response (200, 403, or directory listing) rather than a 404 error, indicating the endpoint exists and may be misconfigured
  3. Attempt to access usermgmt.xml via the known path
    Using a web browser or curl, request http://<server>:<port>/client-data/1/collections/0/usermgmt.xml (substitute different numeric values for client_id and collection number if needed)
    Affected if The request returns an XML file containing user management data, plaintext passwords, or Wi-Fi keys
  4. Inspect returned XML for sensitive data exposure
    If usermgmt.xml is successfully retrieved, open the file and search for plaintext password fields, <PASSWORD>, <WIFI_KEY>, or similar sensitive credential elements
    Affected if The XML contains unencrypted passwords, Wi-Fi keys, or other credentials in plaintext format

You are affected if your installed ManageEngine Desktop Central MSP version is exactly 10.0.137 and the /client-data/ endpoint returns the usermgmt.xml file containing plaintext credentials.

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

Upgrade to ManageEngine Desktop Central MSP build 100157 or later to remediate this vulnerability. Additionally, review and restrict access to the /client-data/ directory and ensure sensitive configuration data is encrypted at rest.

Recommended fix High confidence

ManageEngine Desktop Central MSP build 100157

  1. Back up the current ManageEngine Desktop Central MSP installation and database
  2. Download the fixed build (100157) from the official ManageEngine download portal
  3. Apply the upgrade to the current installation following ManageEngine's standard upgrade procedures
  4. Verify the upgrade was successful by checking the build number in the application
  5. Confirm the vulnerability is resolved by ensuring /client-data/ URLs are no longer accessible without proper authentication

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

Fix this in Manageengine Desktop Central Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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