# CVE-2020-6627: Command injection in n/a

> Attackers can execute arbitrary OS commands on Seagate Central NAS devices via the web-management interface, potentially compromising the system.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 6 Dec 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-6q9w-5qvx-ggjm

## What is CVE-2020-6627?

CVE-2020-6627 is a critical command injection vulnerability in n/a, published on 6 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The web-management application on Seagate Central NAS STCG2000300, STCG3000300, and STCG4000300 devices allows OS command injection via mv_backend_launch in cirrus/application/helpers/mv_backend_helper.php by leveraging the "start" state and sending a check_device_name request.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2020-6627?

It affects 3 products.


Products: Seagate Stcg2000300 Firmware, Seagate Stcg3000300 Firmware, Seagate Stcg4000300 Firmware.

## How do I fix CVE-2020-6627?

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

## Is CVE-2020-6627 being exploited?

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

Public exploit code:

- Seagate Central Storage 2015.0916 - Unauthenticated Remote Command Execution (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-6627 and fix it if it is affected.

What it is: CVE-2020-6627 is a critical command injection vulnerability in n/a, published on 6 Dec 2022. 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-2020-6627 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-2020-6627/ (Markdown: https://insights.sbomify.com/CVE-2020-6627/index.md)
```

## Sources

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

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