CVE-2022-36923
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 · uneditedZoho ManageEngine OpManager, OpManager Plus, OpManager MSP, Network Configuration Manager, NetFlow Analyzer, Firewall Analyzer, and OpUtils before 2022-07-27 through 2022-07-28 (125657, 126002, 126104, and 126118) allow unauthenticated attackers to obtain a user's API key, and then access external APIs.
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 confidenceUnauthenticated attackers can obtain a user's API key in affected Zoho ManageEngine products (OpManager, OpManager Plus, OpManager MSP, Network Configuration Manager, NetFlow Analyzer, Firewall Analyzer, and OpUtils) due to an authentication bypass flaw. The stolen API key can then be used to access external APIs without proper authorization.
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= 12.5= 12.6= 12.5= 12.6= 12.5= 12.6= 12.5= 12.6= 12.5= 12.6= 12.5= 12.6= 12.5= 12.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed ManageEngine productAccess the web interface or check the product name in the application server. Look at the login page or header to confirm which product from the list (OpManager, OpManager Plus, OpManager MSP, Network Configuration Manager, NetFlow Analyzer, Firewall Analyzer, or OpUtils) is running.Affected if The product is any of the seven affected products listed in the CVE.
-
Check the product version numberLocate the version information in the application's About page, Help menu, or footer of the web interface. The affected versions are 12.5 and 12.6.Affected if The installed version is exactly 12.5 or exactly 12.6.
-
Verify the build versionCheck the build or build number in the application's About or version details section. Vulnerable builds are those prior to build 126118.Affected if The build number is below 126118 for versions 12.5 or 12.6.
-
Assess network exposure of the web interfaceDetermine if the application's web interface is accessible from untrusted networks or the internet. This is an unauthenticated vulnerability, so remote attackers can exploit it without any credentials.Affected if The web interface is exposed to the internet or untrusted networks without proper network segmentation or authentication proxies.
-
Review access logs for unusual API key requestsExamine server access logs for suspicious requests to API endpoints, particularly those that may indicate attempts to bypass authentication or retrieve API keys without valid credentials.Affected if There are unauthorized API requests in the logs or evidence of API key exfiltration.
You are affected if you are running any of the seven ManageEngine products at version 12.5 or 12.6 with a build number below 126118, especially if the web interface is network-accessible.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the vendor-released patches (build versions 126118 and later for the mentioned builds) to affected products immediately, as this is an unauthenticated vulnerability with high severity.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36923 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-36923 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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