Manageengine OpmanagerApplication · Zohocorp

CVE-2020-12116

HIGH · 7.5 CVSS v3.1 Published 2020-05-07
Fix available
A fix is available. Upgrade to after 12.3 or later.
See remediation →
84/100
Remediation priority · High
High EPSS 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 Stable build before 124196 and Released build before 125125 allows an unauthenticated attacker to read arbitrary files on the server by sending a crafted request.

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 contains an unauthenticated arbitrary file read vulnerability in builds before 124196 (Stable) and 125125 (Released). Attackers can craft malicious requests to read any file on the server filesystem, potentially exposing sensitive configuration files, credentials, or source code.

MitigationUpdate OpManager to Stable build 124196 or Released build 125125 or later. As a temporary compensating control, restrict network access to the OpManager interface to trusted IPs only.

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= 12.4= 12.5

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 OpManager installation and version
    Locate the OpManager installation directory and locate the version or build file (commonly version.txt, buildinfo, or similar release metadata within the OpManager home directory)
    Affected if The installed build number is less than 124196 (Stable release) or less than 125125 (Released version), or the version displays as 12.3, 12.4, or 12.5 without a build number in the safe range
  2. Check the product build number
    Access the OpManager web interface and navigate to the About or Support page, or check the build.properties file in the OpManager/conf directory
    Affected if The build number shown is below 124196 or 125125 depending on the release track
  3. Verify the exact version string
    In the OpManager administration console, locate the version information typically found under Help > About or the dashboard summary
    Affected if The version is reported as 12.3.x, 12.4.x, or 12.5.x where the build is earlier than the fixed releases
  4. Confirm network exposure
    Determine if the OpManager web interface is accessible from untrusted networks (check firewall rules, reverse proxy configurations, or direct internet exposure)
    Affected if OpManager is reachable from networks outside the trusted administrative zone and the version is vulnerable
  5. Review access logs for suspicious file read patterns
    Examine HTTP access logs in OpManager/logs directory for requests containing directory traversal patterns (such as ../../) targeting sensitive paths
    Affected if Unauthenticated requests with traversal sequences accessing system files are present in the logs

If OpManager is installed with a version of 12.3, 12.4, or 12.5 or a build number below 124196 (Stable) or 125125 (Released), and the interface is network-accessible, the environment is affected by this unauthenticated arbitrary file read vulnerability.

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 12.3
Interim mitigation

Update OpManager to Stable build 124196 or Released build 125125 or later. As a temporary compensating control, restrict network access to the OpManager interface to trusted IPs only.

Fix this in Manageengine Opmanager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-12116 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2020-12116 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