# CVE-2015-7709: Auth bypass in n/a

> Remote attackers can bypass authentication and execute arbitrary commands on Western Digital Arkeia Backup Agent via crafted requests.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2015
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-6hjv-6w26-7pf5

## What is CVE-2015-7709?

CVE-2015-7709 is a critical authentication bypass vulnerability in n/a, published on 5 Oct 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The arkeiad daemon in the Arkeia Backup Agent in Western Digital Arkeia 11.0.12 and earlier allows remote attackers to bypass authentication and execute arbitrary commands via a series of crafted requests involving the ARKFS_EXEC_CMD operation.

Weakness: CWE-264

## Which versions are affected by CVE-2015-7709?

It affects 1 product.


Products: Arkeia Western Digital Arkeia.

## How do I fix CVE-2015-7709?

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

## Is CVE-2015-7709 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-7709 exists.

Public exploit code:

- Western Digital Arkeia Remote Code Execution (metasploit)
- Western Digital Arkeia < 11.0.12 - Remote Code Execution (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-7709 and fix it if it is affected.

What it is: CVE-2015-7709 is a critical authentication bypass vulnerability in n/a, published on 5 Oct 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-7709 exists.

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-2015-7709/ (Markdown: https://insights.sbomify.com/CVE-2015-7709/index.md)
```

## Sources

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

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