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

> Remote attackers can read arbitrary files and execute PHP code via directory traversal in the lang Cookie parameter of the WD Arkeia virtual appliance.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wqpr-5jgg-vf8q

## What is CVE-2014-2846?

CVE-2014-2846 is a high-severity path traversal vulnerability in n/a, published on 28 Apr 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in opt/arkeia/wui/htdocs/index.php in the WD Arkeia virtual appliance (AVA) with firmware before 10.2.9 allows remote attackers to read arbitrary files and execute arbitrary PHP code via a ..././ (dot dot dot slash dot slash) in the lang Cookie parameter, as demonstrated by a request to login/doLogin.

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

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

It affects 1 product.


Products: Westerndigital Arkeia Virtual Appliance Firmware.

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

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

## Is CVE-2014-2846 being exploited?

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

Public exploit code:

- WD Arkeia Virtual Appliance 10.2.9 - Local File Inclusion (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2846 is a high-severity path traversal vulnerability in n/a, published on 28 Apr 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-2846 in the wild and no public exploit code.

Affected product: n/a. 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-2846/ (Markdown: https://insights.sbomify.com/CVE-2014-2846/index.md)
```

## Sources

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

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