CVE-2017-16846
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 · uneditedZoho ManageEngine Applications Manager 13 before build 13530 allows SQL injection via the /manageApplications.do?method=AddSubGroup haid 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 confidenceSQL injection vulnerability in Zoho ManageEngine Applications Manager versions before build 13530 allows unauthenticated remote attackers to inject arbitrary SQL queries through the haid parameter in the /manageApplications.do?method=AddSubGroup endpoint. This can lead to complete database compromise including data exfiltration and potential remote code execution.
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= 13.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Applications Manager installation and versionLocate the Applications Manager installation directory and check the build number in the version file or about page. Typical locations include the installation root folder or within the UI via Help > About. The build number is typically displayed as a numeric value (e.g., 13500, 13529, 13530).Affected if The installed build number is below 13530 (e.g., 13500, 13520, 13529).
-
Verify the vulnerable endpoint is accessibleCheck if the URL /manageApplications.do?method=AddSubGroup is accessible from the network. This can be confirmed by accessing the management console URL and navigating to the AddSubGroup functionality or by testing the endpoint directly with an HTTP request.Affected if The endpoint responds and accepts the haid parameter without authentication, indicating the vulnerable code path is present.
-
Confirm network exposure of the management interfaceDetermine if the Applications Manager web interface is exposed to untrusted networks. Review firewall rules, reverse proxy configurations, or cloud security groups that allow external access to port 8080, 8443, or the configured HTTP/HTTPS management port.Affected if The management interface is accessible from untrusted networks (such as the internet or less-trusted internal segments) without VPN or authentication barriers.
You are affected if your installed build of Applications Manager 13.0 is below 13530 AND the management interface with the vulnerable endpoint is accessible to the network where the attacker resides.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to Applications Manager build 13530 or later. If immediate patching is not possible, consider restricting network access to the management interface and implementing WAF rules for the affected endpoint.
Applications Manager 13 build 13530 or later
- 1. Identify current build number by navigating to Help > About in Applications Manager
- 2. Download the latest build (13530 or later) from the official ManageEngine download page: https://www.manageengine.com/products/applications-manager/download.html
- 3. Back up the existing Applications Manager database and configuration files
- 4. Stop the Applications Manager service
- 5. Run the installer/updater to install the new build
- 6. Start the Applications Manager service and verify the build number in Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-16846 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-16846 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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