dbcve.org
Manageengine Supportcenter PlusApplication · Zohocorp

CVE-2022-36412

CRITICAL · 9.8 CVSS v3.1 Published 2022-07-26
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
In Zoho ManageEngine SupportCenter Plus before 11023, V3 API requests are vulnerable to authentication bypass. (An API request may, in effect, be executed with the credentials of a user who authenticated in the past.)

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 SupportCenter Plus versions before 11023 contain an authentication bypass vulnerability in the V3 API where API requests can be executed using the credentials of a user who authenticated in the past, effectively allowing unauthorized access by replaying or reusing stale authentication tokens.

MitigationUpgrade to ManageEngine SupportCenter Plus version 11023 or later to remediate this vulnerability.

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 Supportcenter PlusApplication
Affected:= 11.0

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. Check installed SupportCenter Plus version
    Locate the product version information in the SupportCenter Plus admin console (typically under Admin > Support Center > General Settings) or check the installation directory for a version file. Compare the version number to the affected range (versions before 11023).
    Affected if The installed version is 11.0 or any build lower than 11023.
  2. Verify V3 API endpoint accessibility
    Attempt to access the V3 API endpoint (typically at /api/v3/ or /api/v3/some_endpoint) on the SupportCenter Plus server without valid authentication or using a known stale token.
    Affected if The V3 API endpoint responds to requests, indicating the API is enabled.
  3. Test token reuse with expired credentials
    Capture or obtain a stale authentication token from a previously authenticated session and attempt to use it to access the V3 API. Observe if the request succeeds when it should fail.
    Affected if Requests to the V3 API succeed using authentication tokens from past sessions that should no longer be valid.
  4. Inspect authentication token validity rules
    Review the SupportCenter Plus configuration files or authentication settings to determine how long authentication tokens remain valid and whether there is proper expiration enforcement.
    Affected if Tokens do not expire or have excessively long validity periods, allowing replay of old credentials.

You are affected if SupportCenter Plus version is 11.0 or any build below 11023 AND the V3 API is accessible, allowing stale authentication tokens to be replayed successfully.

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 SupportCenter Plus version 11023 or later to remediate this vulnerability.

Recommended fix High confidence

Version 11023 or later

  1. 1. Check current version of ManageEngine SupportCenter Plus by navigating to the Admin tab > Product License section
  2. 2. If version is below 11023, download the latest version 11023 or later from the official ManageEngine downloads page (www.manageengine.com)
  3. 3. Take a complete backup of the SupportCenter Plus database and configuration files
  4. 4. Stop the SupportCenter Plus service before upgrading
  5. 5. Run the installer for version 11023 or later on the server
  6. 6. Follow the on-screen upgrade wizard instructions
  7. 7. Once upgrade completes, restart the SupportCenter Plus service
  8. 8. Verify the upgrade was successful by checking the version in Admin > Product License

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

Fix this in Manageengine Supportcenter Plus 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 help mitigating

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-2022-36412 — 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-36412 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