dbcve.org
Manageengine Applications ManagerApplication · Zohocorp

CVE-2019-19649

CRITICAL · 9.8 CVSS v3.1 Published 2019-12-11
Fix available
A fix is available. Upgrade to 13.7 or later.
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 before 13620 allows a remote unauthenticated SQL injection via the SyncEventServlet eventid parameter to the SyncEventServlet.java doGet 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 confidence

Zoho ManageEngine Applications Manager versions before 13620 contain an unauthenticated SQL injection vulnerability in the SyncEventServlet eventid parameter of the doGet function, allowing remote attackers to execute arbitrary SQL commands without credentials.

MitigationUpgrade to Applications Manager version 13620 or later to remediate this vulnerability. Consider deploying WAF rules to block SQL injection attempts on the SyncEventServlet endpoint as an interim 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 Applications ManagerApplication
Affected:< 13.7

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 if Zoho ManageEngine Applications Manager is installed
    Look for the Applications Manager installation directory, typically under ManageEngine/AppManager or similar paths. Check for the AppManager web application in your application server (such as the 'working' directory containing 'AppManager' folders).
    Affected if The product is not installed or not present on the system being assessed.
  2. Determine the installed version build number
    Check the build number in the Applications Manager web interface by navigating to Help -> About, or locate the version.txt/build.info file in the installation directory. The build number is displayed as a numeric value (for example, 13580 for versions before 13620).
    Affected if The build number is less than 13620, indicating the version is before the patched release.
  3. Verify the version corresponds to pre-13.7 releases
    Compare the identified build number or version to 13620. Versions with build numbers below 13620 correspond to releases before version 13.7.
    Affected if The installed version is a pre-13.7 release (build number below 13620).
  4. Confirm the SyncEventServlet endpoint is accessible
    Attempt to access the vulnerable endpoint URL pattern: /syncEvent.do?eventid=<test_value> through the application's web interface or directly via HTTP request. This servlet handles event synchronization requests.
    Affected if The SyncEventServlet responds to requests, indicating the vulnerable component is exposed.
  5. Check network accessibility of the application
    Verify whether the Applications Manager web interface is accessible from network locations. Since this is an unauthenticated SQL injection, any network-accessible instance with the vulnerable version is exploitable.
    Affected if The application is reachable over the network (LAN or WAN) without authentication barriers.

If the installed Applications Manager build number is below 13620 (pre-13.7) and the SyncEventServlet endpoint is network-accessible, the environment is affected by CVE-2019-19649.

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

Upgrade to Applications Manager version 13620 or later to remediate this vulnerability. Consider deploying WAF rules to block SQL injection attempts on the SyncEventServlet endpoint as an interim control.

Recommended fix High confidence

Version 13.7 (build 13620) or later

  1. Back up the current ManageEngine Applications Manager installation and database
  2. Stop the Applications Manager service
  3. Download version 13.7 (build 13620) or later from the official ManageEngine website
  4. Install the upgraded version following the standard upgrade procedure
  5. Start the Applications Manager service
  6. Verify the SyncEventServlet is functioning correctly and 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
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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