CVE-2019-19650
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 before 13640 allows a remote authenticated SQL injection via the Agent servlet agentid parameter to the Agent.java process function.
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's Agent servlet (agentid parameter in Agent.java process function) allows authenticated remote attackers to inject arbitrary SQL queries. The vulnerability affects versions prior to 13640.
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.7CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify if Zoho ManageEngine Applications Manager is installedLocate the Applications Manager installation directory and look for the main executable or service (typically named 'ApplicationsManager' or similar). Check for the 'buildno' or version file in the installation folder.Affected if The product is not installed or cannot be located.
-
Determine the installed version numberLocate the version or build number file in the Applications Manager installation directory. This is typically displayed in the web UI login page or in an 'about' section, and is often stored in a 'version.txt' or 'build.info' file.Affected if The version is not 13640 or later (or build number is below 13640).
-
Verify the Agent servlet is accessibleCheck if the Agent servlet endpoint is exposed. This is typically accessed via a URL path containing '/agent' or '/Agent' in the Applications Manager web interface. Attempt to access this endpoint from an authorized network.Affected if The Agent servlet endpoint is publicly or unrestrictedly accessible over the network.
-
Confirm authentication status for the web interfaceReview the Applications Manager authentication configuration to determine if local database authentication or external authentication (like AD/LDAP) is enabled. Check whether default admin credentials have been changed.Affected if Valid user credentials exist or can be obtained for the Applications Manager interface.
A user is affected if Applications Manager is installed with a version build number below 13640, the Agent servlet is network-accessible, and valid authentication credentials are available.
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.
From vendor data13.7
Upgrade to Applications Manager version 13640 or later which includes the vendor patch. Alternatively, implement input validation and parameterized queries in the Agent.java code if the patch cannot be applied immediately.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19650 — 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-2019-19650 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