CVE-2019-19800
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 14 before 14520 allows a remote unauthenticated attacker to disclose OS file names via FailOverHelperServlet.
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 confidenceZoho ManageEngine Applications Manager versions before 14 build 14520 contains a path disclosure vulnerability in FailOverHelperServlet. A remote unauthenticated attacker can send specially crafted requests to this servlet to reveal operating system file names on the affected server, potentially aiding further attacks.
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= 14.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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 the installed Applications Manager version and build numberLog into the ManageEngine Applications Manager admin console and navigate to the About page (typically under Help > About) or check the build.info file in the installation directory to find the exact build number.Affected if The build number displayed is less than 14520 (e.g., 14500, 14400, etc.)
-
Confirm the FailOverHelperServlet endpoint is accessibleSend a crafted HTTP request to the FailOverHelperServlet endpoint. The typical URL pattern is: http(s)://<server>:<port>/servlet/FailOverHelperServlet or /services/FailOverHelperServlet. Use a tool like curl with a malformed request parameter.Affected if The servlet responds with any error message or output that reveals file system paths (e.g., absolute file paths in error messages, stack traces, or directory listings).
-
Check for path disclosure in servlet responsesExamine the HTTP response body from the FailOverHelperServlet for file paths, directory structures, or stack traces that expose the server's file system layout.Affected if The response contains absolute Windows or Linux paths (such as C:\ or /opt/ or /home/) indicating the server's internal directory structure.
-
Verify network exposure of the ManageEngine web interfaceDetermine if the Applications Manager web console is directly accessible from the internet or untrusted networks by checking firewall rules, reverse proxy configurations, or networkACL settings.Affected if Port 8080 (default HTTP) or 8443 (default HTTPS) is exposed to untrusted networks without VPN or firewall restrictions, making the servlet reachable by remote unauthenticated attackers.
A user is affected if their ManageEngine Applications Manager is version 14.0 with a build number below 14520 and the FailOverHelperServlet is accessible, causing file paths to be disclosed in responses.
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 dataUpgrade ManageEngine Applications Manager to version 14 build 14520 or later to remediate this vulnerability. If immediate patching is not possible, consider restricting network access to the Management console via firewall rules or VPN.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19800 — 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-19800 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