dbcve.org
Manageengine OpmanagerApplication · Zohocorp

CVE-2018-20173

CRITICAL · 9.8 CVSS v3.0 Published 2018-12-17
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
Zoho ManageEngine OpManager 12.3 before 123238 allows SQL injection via the getGraphData API.

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 OpManager 12.3 before build 123238 contains an SQL injection vulnerability in the getGraphData API. Attackers can exploit this by sending crafted SQL queries through the API endpoint, potentially allowing unauthorized access to, modification of, or complete compromise of the underlying database.

MitigationUpdate ManageEngine OpManager to version 12.3 build 123238 or later to apply the vendor patch. If immediate patching is not feasible, restrict network access to the OpManager administrative interface and implement WAF rules to detect SQL injection attempts.

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 OpmanagerApplication
Affected:= 12.3

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 ManageEngine OpManager installation
    Locate the ManageEngine OpManager installation directory or check for the OpManager service running on the server. Common installation paths include C:\ManageEngine\OpManager or /opt/ManageEngine/OpManager on Linux.
    Affected if OpManager is not installed on the system.
  2. Identify the OpManager version and build number
    Access the OpManager web interface and navigate to the About or Help section, or check the build number file in the installation directory (typically called build.txt or version.conf). The build number is displayed as a numeric value.
    Affected if The build number cannot be determined or is not visible.
  3. Compare the installed build to the patched version
    Compare the identified build number to the fixed version 123238. The vulnerability affects builds of OpManager 12.3 with build numbers lower than 123238.
    Affected if The installed build number is lower than 123238 (for example, 123200, 123100, etc.).
  4. Verify getGraphData API accessibility
    Check if the getGraphData API endpoint is accessible by attempting to access it through the web interface or reviewing the web server configuration. The endpoint is typically at /api/getGraphData or similar REST path within the OpManager application.
    Affected if The API endpoint is exposed and accessible without additional authentication controls.
  5. Review web access logs for SQL injection patterns
    Examine the OpManager web access logs (located in the logs directory of the installation) for requests to the getGraphData endpoint containing SQL injection patterns such as UNION SELECT, OR 1=1, or other SQL keywords in parameter values.
    Affected if Suspicious SQL injection payloads are found in the access logs targeting the getGraphData API.

A system is affected if ManageEngine OpManager 12.3 is installed with a build number lower than 123238 and the getGraphData API endpoint is accessible.

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

Update ManageEngine OpManager to version 12.3 build 123238 or later to apply the vendor patch. If immediate patching is not feasible, restrict network access to the OpManager administrative interface and implement WAF rules to detect SQL injection attempts.

Recommended fix High confidence

OpManager 12.3 build 123238 or later

  1. 1. Identify current OpManager version by checking the About section in the admin console or checking the build number in the installation
  2. 2. If the current build is earlier than 123238, plan for upgrade to OpManager 12.3 build 123238 or later
  3. 3. Schedule a maintenance window for the upgrade procedure
  4. 4. Back up the OpManager database and configuration files before proceeding
  5. 5. Download OpManager 12.3 build 123238 or later from the official ManageEngine download portal
  6. 6. Apply the upgrade following ManageEngine's standard upgrade documentation
  7. 7. Verify the upgrade was successful by checking the build number after installation
  8. 8. Test the getGraphData API functionality to ensure proper operation
Caveat Minor version upgrades within 12.x typically maintain backward compatibility; however, test in staging before production deployment

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

Fix this in Manageengine Opmanager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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