dbcve.org
Manageengine Servicedesk Plus MspApplication · Zohocorp

CVE-2022-32551

HIGH · 7.5 CVSS v3.1 Published 2022-07-02
Fix available
A fix is available. Upgrade to 10.6 or later.
See remediation →
84/100
Remediation priority · High
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 ServiceDesk Plus MSP before 10604 allows path traversal (to WEBINF/web.xml from sample/WEB-INF/web.xml or sample/META-INF/web.xml).

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 ServiceDesk Plus MSP before version 10604 is vulnerable to path traversal, allowing attackers to access sensitive configuration files like WEB-INF/web.xml by manipulating file paths in requests to sample/WEB-INF/web.xml or sample/META-INF/web.xml. This can expose application configuration, credentials, and potentially lead to further compromise.

MitigationApply vendor patch version 10604 or later to remediate the path traversal vulnerability. Verify that input validation properly sanitizes file path parameters to prevent directory traversal attacks.

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 Servicedesk Plus MspApplication
Affected:< 10.6= 10.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
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 ServiceDesk Plus MSP version
    Access the ServiceDesk Plus MSP admin console or check the installation directory for version information. Typically found in the admin panel under 'About' or in the product's release notes. Compare against the affected versions: less than 10.6 or equal to 10.6.
    Affected if Installed version is less than 10.6 or exactly version 10.6
  2. Verify web server is accessible
    Confirm the ServiceDesk Plus MSP web interface is running and reachable on its configured port (default 8080 or 8443 for HTTPS).
    Affected if The web application is exposed and accessible over the network
  3. Test for vulnerable path access
    Attempt an HTTP GET request to the endpoints sample/WEB-INF/web.xml and sample/META-INF/web.xml on the ServiceDesk Plus MSP server.
    Affected if Either endpoint returns the actual file contents instead of a 404 or access denied response, indicating the path traversal is exploitable

The environment is affected if ServiceDesk Plus MSP version is less than 10.6 or exactly 10.6 AND the web application is accessible AND the sample/WEB-INF/web.xml or sample/META-INF/web.xml paths return file contents rather than being blocked.

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
Upgrade available Upgrade to 10.6 or later
Fixed in 10.6
Interim mitigation

Apply vendor patch version 10604 or later to remediate the path traversal vulnerability. Verify that input validation properly sanitizes file path parameters to prevent directory traversal attacks.

Recommended fix High confidence

ServiceDesk Plus MSP 10604 or later

  1. 1. Check current ServiceDesk Plus MSP version by navigating to About page in the admin console
  2. 2. Backup the entire ServiceDesk Plus MSP installation directory and database
  3. 3. Download ServiceDesk Plus MSP version 10604 or later from the official ManageEngine download page
  4. 4. Stop the ServiceDesk Plus MSP service before upgrading
  5. 5. Run the upgrade installer following the vendor's upgrade documentation
  6. 6. After upgrade completes, start the ServiceDesk Plus MSP service
  7. 7. Verify the upgrade by checking the version number and testing critical functionality

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

Fix this in Manageengine Servicedesk Plus Msp Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
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,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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