CVE-2014-9372
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 UploadAccountActivities servlet in ManageEngine Password Manager Pro (PMP) before 7103 allows remote attackers to delete arbitrary files via a .. (dot dot) in a 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 UploadAccountActivities servlet of ManageEngine Password Manager Pro allows remote attackers to delete arbitrary files by using '..' sequences in filenames, bypassing intended directory boundaries.
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<= 7.1CVSS 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
- None
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:P/A:P
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.
-
Verify Password Manager Pro is installedLocate the Password Manager Pro installation directory or check running services for the PMP application serverAffected if Password Manager Pro is present and running on the system
-
Check the installed versionInspect the application version information typically found in the admin console, About page, or version file within the installation directoryAffected if The version number is 7.1 or lower (for example, 7.0, 6.x, or any build prior to 7103)
-
Confirm the UploadAccountActivities servlet is accessibleAttempt to access the servlet endpoint via HTTP/HTTPS at the typical path /servlets/UploadAccountActivities or verify it exists in the deployed web application configurationAffected if The servlet is exposed and responds to requests without authentication restrictions
-
Test for directory traversal vulnerabilitySend a crafted request to the UploadAccountActivities servlet with a filename parameter containing '../' sequences attempting to access paths outside the intended upload directoryAffected if The application allows path traversal sequences in the filename parameter and performs file operations without proper validation, enabling arbitrary file deletion
The environment is affected if Password Manager Pro version 7.1 or lower is running with the UploadAccountActivities servlet exposed and accessible without strict validation on the filename parameter.
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 Password Manager Pro to version 7103 or later to patch the vulnerability; alternatively, implement strict input validation on the filename parameter to reject path traversal sequences.
- Consultation2.0 h
- Implementation4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-9372 — 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-9372 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