dbcve.org
Manageengine Netflow AnalyzerApplication · Zohocorp

CVE-2022-38772

HIGH · 8.8 CVSS v3.1 Published 2022-08-29
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
High EPSS 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
Zoho ManageEngine OpManager, OpManager Plus, OpManager MSP, Network Configuration Manager, NetFlow Analyzer, and OpUtils before 125658, 126003, 126105, and 126120 allow authenticated users to make database changes that lead to remote code execution in the NMAP feature.

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

This vulnerability in Zoho ManageEngine products (OpManager, OpManager Plus, OpManager MSP, Network Configuration Manager, NetFlow Analyzer, and OpUtils) allows authenticated users to manipulate database entries through the NMAP feature, which can be leveraged to achieve remote code execution. The attack requires valid credentials but can lead to full system compromise.

MitigationUpgrade to the patched versions (125658, 126003, 126105, or 126120 depending on the product) and restrict NMAP feature access to only necessary personnel while implementing network segmentation.

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 Netflow AnalyzerApplication
Affected:= 12.5= 12.6
Manageengine Network Configuration ManagerApplication
Affected:= 12.5= 12.6
Manageengine OpmanagerApplication
Affected:= 12.5= 12.6
Manageengine Opmanager MspApplication
Affected:= 12.5= 12.6
Manageengine Opmanager PlusApplication
Affected:= 12.5= 12.6
Manageengine OputilsApplication
Affected:= 12.5= 12.6

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. Identify the installed ManageEngine product
    Determine which Zoho ManageEngine product is deployed in your environment from the list: OpManager, OpManager Plus, OpManager MSP, Network Configuration Manager, NetFlow Analyzer, or OpUtils
    Affected if The product is any of these six affected products
  2. Check the product version
    Locate the installed version number of your ManageEngine product, typically found in the product's About or System Info section, or in the installation directory
    Affected if The installed version is exactly 12.5 or exactly 12.6
  3. Verify NMAP feature access
    Determine whether the NMAP feature is enabled and accessible within the product. This is typically configured in the product's feature settings or administration console
    Affected if The NMAP feature is enabled and accessible to authenticated users

Your environment is affected if you have any of the six listed products installed with version 12.5 or 12.6 and the NMAP feature is enabled for authenticated users.

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 the patched versions (125658, 126003, 126105, or 126120 depending on the product) and restrict NMAP feature access to only necessary personnel while implementing network segmentation.

Recommended fix High confidence

NetFlow Analyzer: 125658+ | OpUtils: 126003+ | OpManager/OpManager Plus/OpManager MSP: 126105+ | Network Configuration Manager: 126120+

  1. 1. Identify which ManageEngine product(s) are affected in your environment from: OpManager, OpManager Plus, OpManager MSP, Network Configuration Manager, NetFlow Analyzer, or OpUtils.
  2. 2. Backup the current installation and database before proceeding with the upgrade.
  3. 3. Download the fixed version of the affected product from the official ManageEngine download portal: https://www.manageengine.com/
  4. 4. For NetFlow Analyzer: upgrade to version 125658 or later.
  5. 5. For OpUtils: upgrade to version 126003 or later.
  6. 6. For OpManager, OpManager Plus, OpManager MSP: upgrade to version 126105 or later.
  7. 7. For Network Configuration Manager: upgrade to version 126120 or later.
  8. 8. Apply the upgrade following the standard ManageEngine upgrade procedure for your platform.

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

Fix this in Manageengine Netflow Analyzer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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