FirefoxosOperating system · Mozilla
CVE-2014-1507
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 DeviceStorage API in Mozilla FirefoxOS before 1.2.2 allows attackers to bypass the media sandbox protection mechanism, and read or modify arbitrary files, via a crafted application that uses a relative pathname for a DeviceStorageFile object.
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 confidenceA directory traversal vulnerability in the DeviceStorage API of Mozilla FirefoxOS before version 1.2.2 allows malicious applications to escape the media sandbox protection by using crafted relative pathnames in DeviceStorageFile objects, enabling unauthorized read and write access to arbitrary filesystem locations.
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
FirefoxosOperating system
<= 1.2= 11.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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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.
-
Identify the FirefoxOS versionOn the FirefoxOS device, go to Settings > About Phone > Software Information to view the FirefoxOS version numberAffected if The version displayed is 1.2 or earlier (such as 1.0, 1.1, or 1.2)
-
Identify the Oracle Solaris versionRun the command 'cat /etc/release' or 'uname -a' in the terminal to display the Oracle Solaris versionAffected if The version shown is exactly Oracle Solaris 11.3
-
Verify if DeviceStorage API is accessibleFor FirefoxOS: Check if applications on the device have permission to use the DeviceStorage API by reviewing app manifest permissions (specifically the 'devicestorage' permission)Affected if Any installed application has been granted devicestorage permission and the FirefoxOS version is 1.2 or earlier
A system is affected if it runs FirefoxOS version 1.2 or earlier, or Oracle Solaris version 11.3, and the DeviceStorage API with sandboxed file access is in use.
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.
dbcve · scopedUpdate FirefoxOS devices to version 1.2.2 or later to obtain the patched DeviceStorage API implementation; if update is unavailable, consider application vetting and device replacement strategies.
FirefoxOS 1.2.2 or later
- 1. Identify all devices running FirefoxOS version 1.2 or earlier
- 2. Upgrade each FirefoxOS device to version 1.2.2 or later to resolve the DeviceStorage API path traversal vulnerability
- 3. Verify the upgrade was successful by checking the OS version on each device
- 4. Test that applications using the DeviceStorage API function correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefoxos
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1507 — 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-1507 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