# CVE-2014-3206: Command injection in n/a

> Remote attackers can execute arbitrary code on Seagate BlackArmor NAS devices via vulnerable parameters in backup management scripts.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Feb 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fqq6-5w3p-gwc5

## What is CVE-2014-3206?

CVE-2014-3206 is a critical command injection vulnerability in n/a, published on 23 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Seagate BlackArmor NAS allows remote attackers to execute arbitrary code via the session parameter to localhost/backupmgt/localJob.php or the auth_name parameter to localhost/backupmgmt/pre_connect_check.php.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Seagate Blackarmor Nas 110 Firmware, Seagate Blackarmor Nas 220 Firmware.

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

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

## Is CVE-2014-3206 being exploited?

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

Public exploit code:

- https://github.com/laccart/CVE-2014-3206 (github_poc): https://github.com/laccart/CVE-2014-3206
- Seagate BlackArmor NAS - Command Injection (nuclei): http/cves/2014/CVE-2014-3206.yaml

## Other vulnerabilities in n/a

- [CVE-2014-3205](https://insights.sbomify.com/CVE-2014-3205/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-3206 is a critical command injection vulnerability in n/a, published on 23 Feb 2018. 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-2014-3206 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-2014-3206/ (Markdown: https://insights.sbomify.com/CVE-2014-3206/index.md)
```

## Sources

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

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