dbcve.org
Manageengine OpmanagerApplication · Zohocorp

CVE-2019-17602

CRITICAL · 9.8 CVSS v3.1 Published 2019-10-15
Fix available
A fix is available. Upgrade to 12.4 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
An issue was discovered in Zoho ManageEngine OpManager before 12.4 build 124089. The OPMDeviceDetailsServlet servlet is prone to SQL injection. Depending on the configuration, this vulnerability could be exploited unauthenticated or authenticated.

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

SQL injection vulnerability in the OPMDeviceDetailsServlet servlet of Zoho ManageEngine OpManager prior to version 12.4 build 124089 allows attackers to inject malicious SQL commands via unsanitized input. Depending on the product configuration, exploitation may be possible without authentication.

MitigationUpgrade to OpManager version 12.4 build 124089 or later to remediate. If immediate patching is not feasible, restrict network access to the affected servlet and implement input validation as a compensating control.

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 OpmanagerApplication
Affected:< 12.4= 12.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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpManager installation version
    Locate the OpManager installation directory and check the version file or login to the web interface and navigate to the About/Help section to view the build number and version (for example, Help > About OpManager).
    Affected if The installed version is any release of OpManager prior to version 12.4, or version 12.4 itself (any build before 124089).
  2. Confirm the exact build number
    In the OpManager web interface, go to the About page or check the build number displayed in the product header/footer. Compare the build number to 124089.
    Affected if The build number is less than 124089 (for example, 124000, 123456) or if only the version "12.4" is shown without a build number or with a build number below 124089.
  3. Verify OPMDeviceDetailsServlet is exposed
    Attempt to access the servlet endpoint directly via HTTP/HTTPS. The typical path pattern is: http(s)://<opmanager_host>:<port>/servlet/OPMDeviceDetailsServlet or similar path under the /servlet/ mapping.
    Affected if The servlet responds (even with an error or redirect) indicating it is accessible and reachable over the network.
  4. Check authentication requirements
    Review the OpManager configuration settings for servlet access controls and determine if the OPMDeviceDetailsServlet is configured to allow unauthenticated requests.
    Affected if The servlet is reachable without providing valid credentials, or the product is configured to allow anonymous or unauthenticated access to this endpoint.

A user is affected if OpManager is installed with version 12.4 or any version prior to 12.4, with a build number below 124089, and the OPMDeviceDetailsServlet is network-accessible (regardless of authentication status).

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

Upgrade to OpManager version 12.4 build 124089 or later to remediate. If immediate patching is not feasible, restrict network access to the affected servlet and implement input validation as a compensating control.

Recommended fix High confidence

ManageEngine OpManager 12.4 build 124089 or later

  1. 1. Backup the current OpManager installation and database before proceeding.
  2. 2. Download ManageEngine OpManager version 12.4 build 124089 or later from the official ManageEngine download portal.
  3. 3. Stop the OpManager service to ensure no active sessions during upgrade.
  4. 4. Install the upgrade following the standard OpManager upgrade procedure.
  5. 5. After upgrade, verify the OPMDeviceDetailsServlet is updated by checking the build number in About page.
  6. 6. Confirm the SQL injection vulnerability is resolved by reviewing release notes for build 124089.
  7. 7. Restart the OpManager service and validate core functionality works correctly.
Caveat Standard upgrade precautions apply - backup data and test in staging environment before production deployment; review release notes for any configuration changes or migration requirements

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

Fix this in Manageengine Opmanager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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 locally
dbcve dependency scanner

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