# CVE-2014-1507: Path traversal in n/a

> Attackers can bypass media sandbox protections to read or modify arbitrary files via a crafted application using relative pathnames in Firefox OS.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r587-wfm5-v67q

## What is CVE-2014-1507?

CVE-2014-1507 is a critical path traversal vulnerability in Oracle Solaris, published on 19 Mar 2014. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Directory 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2014-1507?

It affects 2 products.


Products: Mozilla Firefoxos, Oracle Solaris.

## How do I fix CVE-2014-1507?

No fix has been published for CVE-2014-1507 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-1507 being exploited?

There is no known exploitation of CVE-2014-1507 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-1507 and fix it if it is affected.

What it is: CVE-2014-1507 is a critical path traversal vulnerability in Oracle Solaris, published on 19 Mar 2014. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-1507 in the wild and no public exploit code.

Affected product: Oracle Solaris. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-1507/ (Markdown: https://insights.sbomify.com/CVE-2014-1507/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-1507
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-1507
- OSV: https://osv.dev/vulnerability/CVE-2014-1507

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-1507/
Summaries are generated and may contain mistakes; the official description above is the record.