dbcve.org
Manageengine OpmanagerApplication · Zohocorp

CVE-2021-44514

CRITICAL · 9.8 CVSS v3.1 Published 2021-12-09
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
OpUtils in Zoho ManageEngine OpManager 12.5 before 125490 mishandles authentication for a few audit directories.

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

Zoho ManageEngine OpUtils component fails to properly authenticate access to certain audit directories in versions prior to 125490. This allows unauthenticated attackers to potentially access sensitive audit data and configurations. The vulnerability carries a CVSS 9.8 rating indicating trivial exploitability and potential for complete system compromise.

MitigationUpgrade to ManageEngine OpManager version 125490 or later to obtain the vendor patch. If immediate patching is not feasible, restrict network exposure of the OpManager interface using firewall rules or VPN access.

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.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
High
Availability
High

CVSS:3.1/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. Identify OpManager installation path and version
    Locate the OpManager installation directory (commonly C:\ManageEngine\OpManager or /opt/OpManager) and check the version.txt or about.xml file for the exact build number. Compare this to version 125490.
    Affected if Installed version is 12.5 or any build number below 125490
  2. Verify OpUtils component status
    Check if the OpUtils module is installed and enabled. Look for the OpUtils web application directory within the OpManager deployment (typically in the webapps folder) or check the OpUtils service status.
    Affected if OpUtils component is present and running on the system
  3. Check network exposure of OpManager interface
    Review firewall rules, reverse proxy configurations, or network ACLs to determine if the OpManager web interface (default ports 8060, 8062, or 443) is accessible from untrusted networks or the internet.
    Affected if OpManager web interface is exposed to unauthenticated network access
  4. Inspect audit directory access controls
    Examine the audit directory permissions and the server.xml or web.xml configuration files to verify whether authentication is required for accessing /audit or /OpUtils audit endpoints.
    Affected if Audit directories allow unauthenticated access or authentication is bypassed for these paths

You are affected if OpManager version is 12.5 or any build below 125490 AND the OpUtils component is enabled with unauthenticated network access to audit directories possible.

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 OpManager version 125490 or later to obtain the vendor patch. If immediate patching is not feasible, restrict network exposure of the OpManager interface using firewall rules or VPN access.

Recommended fix Moderate confidence

OpManager 12.5 build 125490 or later

  1. Verify current OpManager version by checking About or version info in the admin console
  2. Download OpManager version 125490 or later from ManageEngine's official download portal
  3. Review ManageEngine OpManager upgrade documentation for your deployment type
  4. Execute the upgrade following standard upgrade procedures (backup database first, stop services, run installer, restart services)
  5. Verify the OpUtils component is accessible and authentication is properly enforced after upgrade
  6. Confirm the build number reflects 125490 or higher

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

Fix this in Manageengine Opmanager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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