dbcve.org
Manageengine Applications ManagerApplication · Zohocorp

CVE-2017-16847

CRITICAL · 9.8 CVSS v3.0 Published 2017-11-16
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 Applications Manager 13 before build 13530 allows SQL injection via the /showresource.do resourceid parameter in a showPlasmaView action.

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 Applications Manager versions 13 before build 13530 contains a SQL injection vulnerability in the /showresource.do endpoint via the resourceid parameter in a showPlasmaView action. An unauthenticated remote attacker can inject malicious SQL queries to potentially access, modify, or delete database contents.

MitigationUpgrade to Zoho ManageEngine Applications Manager build 13530 or later, which includes the fix for this SQL injection 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 Applications ManagerApplication
Affected:= 13.0

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.0/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 installed version of ManageEngine Applications Manager
    Locate the build number in the Applications Manager installation. Typically found in the 'build.conf' file within the installation directory, or by accessing the About page in the admin console (usually /jsp/admin/home.jsp or similar). Look for a build number such as 'build 13530' or similar.
    Affected if The build number is less than 13530 (e.g., build 13xxx versions before 13530)
  2. Confirm the application is the Zoho ManageEngine Applications Manager
    Verify the product name is 'ManageEngine Applications Manager' and the major version is 13. This can be confirmed in the application header, About page, or installation files.
    Affected if The product is Zoho ManageEngine Applications Manager version 13
  3. Verify the vulnerable endpoint is accessible
    Check if the web interface exposes the /showresource.do endpoint. This is typically accessible via HTTP/HTTPS on the port where Applications Manager is running (default port 8080). Attempt to access: http://<server>:<port>/showresource.do
    Affected if The endpoint responds, indicating the web interface is active
  4. Confirm the showPlasmaView action is available
    Test access to the vulnerable action by attempting a request to /showresource.do?action=showPlasmaView&resourceid=test. This can be done via browser or curl command.
    Affected if The application accepts the showPlasmaView action parameter without authentication requirements

The environment is affected if running Zoho ManageEngine Applications Manager version 13 with build number less than 13530, with the /showresource.do endpoint and showPlasmaView action accessible.

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 Zoho ManageEngine Applications Manager build 13530 or later, which includes the fix for this SQL injection vulnerability.

Recommended fix High confidence

ManageEngine Applications Manager 13 build 13530 or later

  1. 1. Identify current build version of ManageEngine Applications Manager by accessing the About section in the admin console
  2. 2. Navigate to ManageEngine Applications Manager download page (www.manageengine.com) and download build 13530 or later
  3. 3. Create a complete backup of the Applications Manager database and configuration files
  4. 4. Stop the Applications Manager service before applying the upgrade
  5. 5. Install the upgraded build (13530 or later) following the standard ManageEngine upgrade procedure
  6. 6. Restart the Applications Manager service after upgrade completion
  7. 7. Verify the fix by confirming the /showresource.do resourceid parameter is properly sanitized and the showPlasmaView action functions correctly
  8. 8. Run internal security scans to confirm the SQL injection vulnerability is resolved

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

Fix this in Manageengine Applications Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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