CVE-2022-40770
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 ServiceDesk Plus versions 13010 and prior are vulnerable to authenticated command injection. This can be exploited by high-privileged users.
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 confidenceZoho ManageEngine ServiceDesk Plus versions 13010 and prior contains an authenticated command injection vulnerability. Attackers with high-privileged user credentials can inject and execute arbitrary operating system commands on the underlying server through the application interface.
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< 13.0= 13.0< 10.6= 10.6< 11.0= 11.0CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify ServiceDesk Plus version and buildAccess the application admin interface and navigate to the About or Version section, typically found under Admin > Applications > Version Details. Alternatively, check the build.info or version file in the installation directory.Affected if Version is 13.0 (any build) or any version below 13.0, or build number is 13010 or prior.
-
Identify ServiceDesk Plus MSP versionIf using the MSP variant, access the MSP product admin console and locate the version/build information in the About or System Information page.Affected if Version is 10.6 (any build) or any version below 10.6.
-
Identify SupportCenter Plus versionIf using SupportCenter Plus, access the admin panel and locate version information typically found in the About or Product Information section.Affected if Version is 11.0 (any build) or any version below 11.0.
-
Verify presence of high-privileged accountsReview user accounts in the application admin panel and identify accounts with Administrator, Super Admin, or equivalent high-privilege roles. Check for any unexpected or unauthorized admin-level accounts.Affected if Any high-privileged accounts exist in the system, as exploitation requires these credentials.
-
Review application logs for command injection indicatorsExamine application logs in the installation logs directory for entries containing unusual system commands, suspicious script execution, or commands originating from user input fields. Look for patterns like shell metacharacters (;, |, &, $) in log entries.Affected if Logs contain unexpected system commands or shell command executions that were not initiated by known administrators.
A user is affected if their installed version of ServiceDesk Plus, ServiceDesk Plus MSP, or SupportCenter Plus matches the affected version ranges AND the application is accessible to users with high-privileged credentials.
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 data10.611.013.0
Upgrade ServiceDesk Plus to a version newer than 13010 per vendor guidance. Since exploitation requires high-privileged access, immediately review and limit admin-level accounts and monitor for suspicious administrative activity until the patch is applied.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40770 — 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-40770 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