CVE-2014-9373
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 · uneditedDirectory traversal vulnerability in the CollectorConfInfoServlet servlet in ManageEngine NetFlow Analyzer allows remote attackers to execute arbitrary code via a .. (dot dot) in the filename.
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 confidenceDirectory traversal vulnerability in the CollectorConfInfoServlet servlet in ManageEngine NetFlow Analyzer allows remote attackers to execute arbitrary code via '..' (dot dot) sequences in the filename parameter, leading to complete system compromise.
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 dataall versionsCVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 NetFlow Analyzer installationIdentify if ManageEngine NetFlow Analyzer is installed on the system. Check for the product in standard installation directories (such as C:\ManageEngine\NetFlow or /opt/ManageEngine/NetFlow) or look for the ManageEngine service running on common ports like 8080, 8443, or 8090.Affected if The product is installed and running on the system.
-
Check NetFlow Analyzer versionAccess the NetFlow Analyzer web interface and navigate to the About or Admin section to retrieve the installed version number, or check the version file in the installation directory if accessible locally.Affected if Any installed version is vulnerable since all versions are affected.
-
Verify CollectorConfInfoServlet accessibilityAttempt to access the CollectorConfInfoServlet endpoint. The typical path is /servlet/CollectorConfInfoServlet or similar paths under the NetFlow Analyzer context. Use a web browser or curl to send a request to this endpoint.Affected if The servlet responds and is reachable via HTTP/HTTPS.
-
Assess network exposure of the management interfaceDetermine if the NetFlow Analyzer web interface (typically on port 8080 or 8443) is exposed to untrusted networks. Check firewall rules, NAT configurations, and binding addresses in the server configuration to see if the interface listens on 0.0.0.0 or is accessible from outside the local network.Affected if The interface is accessible from untrusted networks or the internet without proper network segmentation.
-
Test for path traversal vulnerabilitySend a crafted request to the CollectorConfInfoServlet containing '../' sequences in the filename parameter (for example: /servlet/CollectorConfInfoServlet?filename=../../../etc/passwd or similar). Observe if the application returns files from outside the expected directory.Affected if The application returns files from outside the intended directory, confirming the path traversal vulnerability is exploitable.
The environment is affected if ManageEngine NetFlow Analyzer is installed and the CollectorConfInfoServlet is network-accessible, since all versions contain the directory traversal vulnerability.
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 dataApply vendor patches for ManageEngine NetFlow Analyzer. Until patched, restrict network access to the servlet and implement input validation to reject path traversal sequences.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-9373 — 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-2014-9373 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