CVE-2023-22964
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 MSP before 10611, and 13x before 13004, is vulnerable to authentication bypass when LDAP authentication is enabled.
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 MSP versions before 10611 (MSP versions) and before 13004 (13x versions) contain an authentication bypass vulnerability that allows unauthenticated or authenticated attackers to circumvent authentication controls when LDAP authentication is enabled. The flaw likely involves improper validation of LDAP authentication responses, enabling attackers to gain unauthorized access to the application and potentially administrative functions.
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= 10.6= 13.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Confirm ServiceDesk Plus MSP installationLocate the ServiceDesk Plus MSP installation by checking for the service process or checking common installation directories. On Windows, open Services and look for 'ManageEngine ServiceDesk Plus - MSP'. On Linux, check for the servicdesk process or the default installation path.Affected if ServiceDesk Plus MSP is installed on the system
-
Identify installed versionAccess the ServiceDesk Plus MSP web interface login page. Navigate to the About page or the Admin > Server Settings section to view the exact version number displayed.Affected if The installed version is 10.6 (MSP) or 13.0 (13x), or any version before 10611 for MSP releases or before 13004 for 13x releases
-
Verify LDAP authentication is enabledLog into the ServiceDesk Plus MSP admin console. Navigate to the LDAP or Active Directory configuration section (typically under Admin > Authentication > LDAP/AD or Settings > LDAP Configuration). Confirm whether LDAP authentication is configured and enabled.Affected if LDAP authentication is enabled and the version falls within the affected range
-
Inspect LDAP configuration settingsIn the LDAP configuration panel, review the authentication settings and connection details. Check if the LDAP directory is properly configured with valid search bases and bind credentials.Affected if LDAP authentication is active and the application version is vulnerable to the bypass
Your environment is affected if ServiceDesk Plus MSP is running with LDAP authentication enabled and the installed version is below 10611 (MSP) or below 13004 (13x).
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.
dbcve · scopedUpgrade ServiceDesk Plus MSP to version 10611 or later (MSP) or version 13004 or later (13x). If immediate patching is not possible, consider temporarily disabling LDAP authentication and using local accounts, or implementing network-level access controls to limit exposure.
For 10.x line: upgrade to build 10611 or later. For 13.x line: upgrade to build 13004 or later.
- 1. Identify your current ServiceDesk Plus MSP build version in the admin console under 'Admin' > 'System' > 'System Information'
- 2. Download the appropriate patch from ManageEngine's official support portal based on your current major version
- 3. For versions 10.x: ensure you upgrade to build 10611 or later
- 4. For versions 13.x: ensure you upgrade to build 13004 or later
- 5. Take a complete backup of the ServiceDesk Plus MSP database and configuration files before upgrading
- 6. Schedule the upgrade during a planned maintenance window
- 7. Apply the upgrade following ManageEngine's standard upgrade procedure
- 8. After upgrade, verify LDAP authentication is functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22964 — 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-2023-22964 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