# CVE-2014-3205: Hardcoded credentials in n/a

> Attackers can use a hard-coded backdoor password to gain unauthorized access to Seagate BlackArmor NAS devices.

- **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-cx2f-7chx-h565

## What is CVE-2014-3205?

CVE-2014-3205 is a critical 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

backupmgt/pre_connect_check.php in Seagate BlackArmor NAS contains a hard-coded password of '!~@##$$%FREDESWWSED' for a backdoor user.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 2 products.


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

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

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

## Is CVE-2014-3205 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-3206](https://insights.sbomify.com/CVE-2014-3206/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-3205 is a critical 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: There is no known exploitation of CVE-2014-3205 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-3205/ (Markdown: https://insights.sbomify.com/CVE-2014-3205/index.md)
```

## Sources

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

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