dbcve.org
Manageengine Desktop CentralApplication · Zohocorp

CVE-2023-4769

HIGH · 8.8 CVSS v3.1 Published 2023-11-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
A SSRF vulnerability has been found in ManageEngine Desktop Central affecting version 9.1.0, specifically the /smtpConfig.do component. This vulnerability could allow an authenticated attacker to launch targeted attacks, such as a cross-port attack, service enumeration and other attacks via HTTP requests.

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

A Server-Side Request Forgery (SSRF) vulnerability in the /smtpConfig.do component of ManageEngine Desktop Central version 9.1.0 allows authenticated attackers to induce the server into making HTTP requests to arbitrary internal or external resources, enabling cross-port attacks and internal service enumeration.

MitigationRestrict access to the /smtpConfig.do endpoint to trusted authenticated users only, implement strict allowlist-based URL validation for SMTP configuration inputs, and apply vendor-provided patches when released. Consider network segmentation to limit the impact of potential SSRF exploitation.

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:= 9.1.0

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

CVSS:3.1/AV:N/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. Confirm ManageEngine Desktop Central is installed
    Look for the Desktop Central installation directory or check running services for ManageEngine Desktop Central. Common installation paths: C:\Program Files\ManageEngine\DesktopCentral on Windows or /opt/ManageEngine/DesktopCentral on Linux.
    Affected if The product is not installed or this is a different product.
  2. Identify the installed version
    Check the version file or About page in the Desktop Central admin console. On Windows, check the version info in the installation directory or the service details. On Linux, check the version file in the installation directory.
    Affected if The installed version is exactly 9.1.0 - this is the only affected version per the CVE.
  3. Verify the /smtpConfig.do endpoint exists
    Access the URL path /smtpConfig.do on the Desktop Central server (e.g., https://your-server:8020/smtpConfig.do or the configured port). Check if the endpoint responds or is reachable.
    Affected if The endpoint returns a valid response or error, indicating it is accessible.
  4. Confirm authentication is configured for Desktop Central
    Review the authentication settings in the Desktop Central admin console under Admin > Authentication. Verify whether the /smtpConfig.do endpoint requires valid credentials.
    Affected if Anonymous or weak authentication is enabled, allowing unauthenticated access to the endpoint.
  5. Check for network exposure of the admin console
    Review firewall rules and network ACLs to determine if the Desktop Central web interface (port 8020 or configured HTTP port) is exposed to untrusted networks or the internet.
    Affected if The admin console is exposed to the internet or untrusted internal networks, increasing exploitation risk.

You are affected only if ManageEngine Desktop Central version 9.1.0 is installed and the /smtpConfig.do endpoint is accessible to untrusted authenticated users or network attackers.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict access to the /smtpConfig.do endpoint to trusted authenticated users only, implement strict allowlist-based URL validation for SMTP configuration inputs, and apply vendor-provided patches when released. Consider network segmentation to limit the impact of potential SSRF exploitation.

Fix this in Manageengine Desktop Central Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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