dbcve.org
Manageengine Desktop CentralApplication · Zohocorp

CVE-2022-23779

MEDIUM · 5.3 CVSS v3.1 Published 2022-03-02
Fix available
A fix is available. Upgrade to 10.1.2137.8 or later.
See remediation →
62/100
Remediation priority · Elevated
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 Desktop Central before 10.1.2137.8 exposes the installed server name to anyone. The internal hostname can be discovered by reading HTTP redirect responses.

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

Zoho ManageEngine Desktop Central before version 10.1.2137.8 exposes the internal server hostname through HTTP redirect responses. An unauthenticated remote attacker can discover the internal network hostname by simply observing the Location header or body of HTTP redirects from the application.

MitigationUpgrade to version 10.1.2137.8 or later. Alternatively, configure reverse proxy or load balancer to rewrite outbound redirect responses to mask internal hostnames.

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.1.2137.8

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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. Identify the installed Desktop Central version
    Log into the Desktop Central admin console and navigate to the About or Settings page to view the version number, or check the Windows Services properties for ManageEngine Desktop Central which displays the version
    Affected if The version is lower than 10.1.2137.8
  2. Determine the application URL base
    Note the URL used to access the Desktop Central web interface, for example https://servername:port or the hostname portion of the URL
    Affected if You have a working URL to test against
  3. Send a request that triggers a redirect
    Using a browser or HTTP tool (curl, Burp, etc.), send a request to an invalid or redirected path such as / nonexistentpath or /config/someinvalidresource and capture the HTTP response
    Affected if The server returns a 30x redirect status code
  4. Examine redirect response headers
    Inspect the Location header in the 30x response and check if it contains an internal hostname (such as an internal domain name, IP address, or machine name) rather than a public-facing hostname
    Affected if The Location header reveals an internal hostname or private IP address that should not be exposed externally
  5. Examine redirect response body
    If the redirect is meta refresh or JavaScript-based, inspect the response body for any exposed internal hostnames in the redirect target URL
    Affected if The response body contains internal network hostnames or private IP addresses

You are affected if the installed version is below 10.1.2137.8 AND HTTP redirect responses expose internal hostnames in the Location header or body.

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 10.1.2137.8 or later
Fixed in 10.1.2137.8
Interim mitigation

Upgrade to version 10.1.2137.8 or later. Alternatively, configure reverse proxy or load balancer to rewrite outbound redirect responses to mask internal hostnames.

Recommended fix High confidence

10.1.2137.8

  1. Create a full backup of the current ManageEngine Desktop Central installation and database
  2. Download version 10.1.2137.8 or later from the official ManageEngine download portal (www.manageengine.com)
  3. Review the official upgrade instructions in the ManageEngine documentation before proceeding
  4. Execute the upgrade following the vendor's standard upgrade procedure
  5. Verify the upgrade was successful by checking the server version information
  6. Test that HTTP redirect responses no longer expose internal hostname information

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

Fix this in Manageengine Desktop Central Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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