Manageengine Adselfservice PlusApplication · Zohocorp

CVE-2024-27310

MEDIUM · 6.5 CVSS v3.1 Published 2024-05-27
Fix available
A fix is available. Upgrade to 6.4 or later.
See remediation →
74/100
Remediation priority · Elevated
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 ADSelfService Plus versions below 6401 are vulnerable to the DOS attack due to the malicious LDAP input.

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 ADSelfService Plus versions before 6401 are vulnerable to denial of service when processing specially crafted LDAP input. The application fails to properly validate or sanitize LDAP queries, allowing an attacker to cause the service to become unresponsive or crash.

MitigationUpgrade ADSelfService Plus to version 6401 or later to remediate this vulnerability. If immediate patching is not possible, consider restricting LDAP access through network segmentation or firewall rules.

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 Adselfservice PlusApplication
Affected:< 6.4= 6.4

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
Low
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L

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 installed ADSelfService Plus version
    Access the product's About or System Information page in the admin console, or check the version file in the installation directory (typically found in the product's main folder or in a 'build' or 'version' file).
    Affected if The installed version is 6.4 or any version lower than 6.4 (for example, 6.3, 6.2, 6.1, etc.). Note that version 6.4 itself is also affected; only version 6401 and later are not vulnerable.
  2. Verify LDAP-based authentication or self-service is configured
    In the ADSelfService Plus admin console, navigate to the LDAP or Directory Service configuration section. Check whether LDAP-based authentication, password reset, or self-service features are enabled and connected to an Active Directory or LDAP directory.
    Affected if LDAP integration is actively configured and in use. The vulnerability is triggered when processing LDAP queries, so LDAP must be enabled for the flaw to be exploitable.
  3. Confirm the build number if running version 6.4
    If the product shows version 6.4, look for a build number or patch level in the About section, installation directory, or release notes. The vulnerable build is 6.4 (any build before build 6401).
    Affected if Running version 6.4 with build number lower than 6401. Versions below 6.4 (such as 6.3.x) are also affected regardless of build number.

You are affected if ADSelfService Plus is running any version below 6.4, or is running version 6.4 with build number below 6401, AND has LDAP-based authentication or self-service features enabled.

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 6.4 or later
Fixed in 6.4
Interim mitigation

Upgrade ADSelfService Plus to version 6401 or later to remediate this vulnerability. If immediate patching is not possible, consider restricting LDAP access through network segmentation or firewall rules.

Recommended fix High confidence

Upgrade to ADSelfService Plus build 6401 or later (version 6.4 build 6401)

  1. Check current ADSelfService Plus version (via Help > About).
  2. Backup the existing installation, database, and configuration files.
  3. Download the fixed version (build 6401 or later) from the official ManageEngine website.
  4. Run the upgrade installer and follow the on-screen instructions.
  5. Restart the ADSelfService Plus service after the upgrade.
  6. Verify the version after upgrade to ensure the fix is applied.

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

Fix this in Manageengine Adselfservice Plus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-27310 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-27310 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