dbcve.org
Manageengine Adselfservice PlusApplication · Zohocorp

CVE-2019-3905

CRITICAL · 10.0 CVSS v3.0 Published 2019-01-03
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
Zoho ManageEngine ADSelfService Plus 5.x before build 5703 has SSRF.

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

Server-Side Request Forgery (SSRF) vulnerability in Zoho ManageEngine ADSelfService Plus versions 5.x prior to build 5703 allows remote attackers to make the application perform requests to arbitrary servers, potentially accessing internal resources or services.

MitigationUpgrade to ADSelfService Plus build 5703 or later to address the SSRF 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 Adselfservice PlusApplication
Affected:= 5.0= 5.1= 5.2= 5.3= 5.4= 5.5= 5.6= 5.7

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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. Confirm ADSelfService Plus is installed
    Check for the application process or installation directory. On Windows, look for 'ADSelfService Plus' in Programs or check for the service. On Linux, check /opt/manageengine/adselfserviceplus or similar paths.
    Affected if The application is installed and running on the system
  2. Locate the build version file
    Navigate to the ADSelfService Plus installation directory and find the build number. Common locations: 'build.txt' in the root directory, or within the 'conf' folder, or check the 'product.info' file.
    Affected if Unable to locate version information indicates the product may not be properly installed
  3. Read the installed build number
    Open the build version file (build.txt, build.number, or similar) and note the exact build number displayed.
    Affected if The displayed build number is missing or unreadable
  4. Compare build to vulnerable range
    Compare your installed build number against the affected versions: 5.0 through 5.7 with build numbers earlier than 5703. If running 5.x series with build < 5703, you are affected.
    Affected if Build number is 5.0, 5.1, 5.2, 5.3, 5.4, 5.5, 5.6, or 5.7 AND the specific build is less than 5703
  5. Verify web interface accessibility
    ADSelfService Plus SSRF is exploitable through the web application. Check if the web interface is accessible on default ports 8888 (HTTP) or 443/8443 (HTTPS). Attempt to access the login page or check if the application responds to HTTP requests.
    Affected if The web interface is exposed and the version/build is in the vulnerable range

You are affected if ADSelfService Plus version 5.x (build 5702 or earlier) is installed and the web interface is accessible, as the SSRF vulnerability exists in the application web requests functionality.

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 ADSelfService Plus build 5703 or later to address the SSRF vulnerability.

Recommended fix High confidence

ManageEngine ADSelfService Plus build 5703 or later

  1. 1. Back up the ADSelfService Plus database and configuration files before starting the upgrade process.
  2. 2. Download the latest version of ManageEngine ADSelfService Plus (build 5703 or later) from the official ManageEngine download page: www.manageengine.com/products/active-directory-self-service/
  3. 3. Stop the ADSelfService Plus service on the server.
  4. 4. Run the installer for the new build (5703 or later).
  5. 5. Follow the on-screen upgrade wizard instructions, pointing to the existing installation directory when prompted.
  6. 6. After upgrade completes, start the ADSelfService Plus service.
  7. 7. Verify the SSRF vulnerability is patched by checking that the affected endpoint no longer allows arbitrary URL fetching.
  8. 8. Test that normal ADSelfService Plus functionality (password reset, self-service) continues to work properly.
Caveat Review release notes for build 5703 for any changes to existing functionality or configuration requirements before upgrading

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
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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