dbcve.org
Manageengine Applications ManagerApplication · Zohocorp

CVE-2017-16849

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 /MyPage.do?method=viewDashBoard forpage parameter.

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 Zoho ManageEngine Applications Manager 13 (before build 13530) allows remote attackers to inject malicious SQL queries via the forpage parameter in the /MyPage.do endpoint with method=viewDashBoard. The lack of proper input sanitization enables attackers to manipulate database queries, potentially gaining unauthorized access to sensitive data or compromising the entire application database.

MitigationApply vendor patch (build 13530 or later) from Zoho ManageEngine. As immediate compensating controls, implement WAF rules to block SQL injection payloads in the affected parameter and restrict network access to the management interface until the patch is applied.

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 the installed Applications Manager build version
    Access the Applications Manager web UI and navigate to the About page (typically via Help > About or /about.do), or check the build number in the admin console. The build number is displayed as a numeric value.
    Affected if The build number exists and is less than 13530 (for example, 13500, 13400, etc.)
  2. Verify the /MyPage.do endpoint is accessible
    Attempt to access the URL pattern: http(s)://<hostname>:<port>/MyPage.do?method=viewDashBoard from a browser or curl request. A successful HTTP 200 response indicates the endpoint exists.
    Affected if The endpoint responds with HTTP 200 and does not return a 404 or access denied error, meaning the vulnerable endpoint is exposed.
  3. Confirm network exposure of the management interface
    Check if the Applications Manager web console is bound to a non-localhost interface (0.0.0.0) or an external IP address rather than localhost only. Inspect network configuration or firewall rules to determine if port 8080 (default) or the configured port is reachable from untrusted networks.
    Affected if The management interface is reachable from network segments outside the trusted internal network, enabling remote attackers to reach the vulnerable endpoint.

You are affected if your installed build is before 13530 AND the /MyPage.do endpoint with viewDashBoard method is accessible from your network.

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

Apply vendor patch (build 13530 or later) from Zoho ManageEngine. As immediate compensating controls, implement WAF rules to block SQL injection payloads in the affected parameter and restrict network access to the management interface until the patch is applied.

Recommended fix High confidence

ManageEngine Applications Manager 13 build 13530 or later

  1. 1. Backup the current ManageEngine Applications Manager installation and database before proceeding
  2. 2. Navigate to the ManageEngine Applications Manager download page or customer portal
  3. 3. Download Applications Manager version 13 with build 13530 or later
  4. 4. Follow the standard ManageEngine upgrade procedure: stop the Application Manager service, run the upgrade installer, and follow on-screen instructions
  5. 5. After upgrade completes, start the Application Manager service
  6. 6. Verify the fix by testing the /MyPage.do?method=viewDashBoard endpoint with the forpage parameter to confirm SQL injection is no longer exploitable
  7. 7. Review application logs to ensure no exploitation occurred prior to patching
Caveat Review ManageEngine release notes for build 13530 for any specific configuration or feature changes; standard upgrade risks apply (test in non-production first)

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

Fix this in Manageengine Applications Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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