CVE-2014-1973
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 NextApp File Explorer application before 2.1.0.3 for Android allows remote attackers to overwrite or create arbitrary files via a crafted 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 confidenceThis is a directory traversal vulnerability in the NextApp File Explorer Android application versions prior to 2.1.0.3. The app fails to properly validate or sanitize filenames passed to file operations, allowing an attacker to use crafted filenames containing path traversal sequences (such as '../') to write to arbitrary locations on the device's filesystem. This could enable overwriting existing files or creating new files in unintended directories.
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<= 2.0.2.3CVSS 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
- None
AV:N/AC:L/Au:N/C:N/I:P/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.
-
Verify NextApp File Explorer is installedOn the Android device, go to Settings > Apps > Look for 'File Explorer' or 'NextApp File Explorer' in the installed applications list, or use ADB command: `adb shell pm list packages | grep -i nextapp`Affected if The application is present on the device
-
Retrieve the installed version numberIn Settings > Apps > File Explorer, check the 'Version' or 'Version name' field displayed under app info, or use ADB: `adb shell dumpsys package com.nextapp.fileexplorer | grep versionName`Affected if A version number is displayed
-
Compare version against affected rangeCompare the installed version to the affected versions: any version <= 2.0.2.3 is vulnerable. Note that versions 2.1.0.3 and later are patched.Affected if Installed version is 2.0.2.3 or any earlier version (e.g., 2.0.2.2, 2.0.1.0, 1.x.x)
A device is affected if NextApp File Explorer version 2.0.2.3 or any earlier version is installed, since the directory traversal flaw exists in those versions.
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 dataUsers should immediately update the NextApp File Explorer application to version 2.1.0.3 or later. Organizations should use mobile device management (MDM) tools to identify and push the patched version to all affected Android devices, verifying successful deployment.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1973 — 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-1973 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