dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-9100

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Zohocorp ManageEngine Analytics Plus versions before 5410 and Zoho Analytics On-Premise versions before 5410 are vulnerable to Path traversal.

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 · moderate confidence

This is a path traversal vulnerability in Zohocorp ManageEngine Analytics Plus and Zoho Analytics On-Premise versions prior to 5410. The flaw allows attackers to access files outside the web root folder using directory traversal sequences (e.g., ../) in user-supplied input, potentially exposing sensitive system files.

MitigationUpgrade to Analytics Plus and Zoho Analytics On-Premise version 5410 or later. Apply input validation on all file path parameters and restrict file system access permissions as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed version of Analytics Plus or Zoho Analytics On-Premise
    Log into the admin console and navigate to the About or Settings section to view the product version, or check the installation directory for a version file. Alternatively, access the login page and look for version information in the footer or help section.
    Affected if The displayed version number is lower than 5410 (for example, 5400, 5300, or any build prior to 5410).
  2. Confirm the product type is affected
    Verify that the installation is either ManageEngine Analytics Plus or Zoho Analytics On-Premise. This vulnerability does not apply to other ManageEngine products or cloud-only Zoho Analytics deployments.
    Affected if The product is Analytics Plus or Zoho Analytics On-Premise and the version is below 5410.
  3. Verify the web server component is running
    Check if the internal Tomcat or internal web server service is active and listening on the configured HTTP/HTTPS ports (typically 8443 or 8080). Use commands like netstat or ss to list active network listeners.
    Affected if The web server is running and accessible, which enables the path traversal attack surface through HTTP requests.
  4. Inspect accessible file path parameters
    Review the application configuration or proxy settings to identify endpoints that accept file path inputs. In a test environment, attempt to send a request with ../ sequences to suspected file upload or export endpoints and observe if directory traversal is possible.
    Affected if Endpoints accepting user-supplied path parameters are accessible without proper input validation, allowing the vulnerability to be exploited.

A user is affected if their Analytics Plus or Zoho Analytics On-Premise installation is version 5410 or lower and the web interface is accessible, since the path traversal flaw can then be triggered via specially crafted requests containing ../ sequences.

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

Upgrade to Analytics Plus and Zoho Analytics On-Premise version 5410 or later. Apply input validation on all file path parameters and restrict file system access permissions as a defense-in-depth measure.

Recommended fix Moderate confidence

version 5410 or later

  1. 1. Identify the current version of ManageEngine Analytics Plus or Zoho Analytics On-Premise currently installed
  2. 2. If the current version is before 5410, plan for an upgrade to version 5410 or later
  3. 3. Download the latest version (5410 or newer) from the official ManageEngine or Zoho Analytics download portal
  4. 4. Before upgrading, perform a complete backup of the existing installation including databases and configuration files
  5. 5. Review release notes for version 5410 to understand any specific upgrade requirements or prerequisites
  6. 6. Execute the upgrade following the standard product upgrade documentation
  7. 7. After upgrade, verify the installation by checking the product version and testing core functionality
  8. 8. Confirm the path traversal vulnerability is resolved by validating that file access is properly restricted

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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