# CVE-2017-12573: Command injection in n/a

> Authenticated attackers can execute arbitrary code on PLANEX CS-W50HD devices via command injection in the NAS settings page.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j822-qpx5-h59x

## What is CVE-2017-12573?

CVE-2017-12573 is a high-severity command injection vulnerability in n/a, published on 24 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered on PLANEX CS-W50HD devices with firmware before 030720. The device has a command-injection vulnerability in the web management UI on NAS settings page "/cgi-bin/nasset.cgi". An attacker can send a crafted HTTP POST request to execute arbitrary code. Authentication is required before executing the attack.

## Which versions are affected by CVE-2017-12573?

It affects 1 product.


Products: Planex Cs-W50hd Firmware.

## How do I fix CVE-2017-12573?

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

## Is CVE-2017-12573 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-12573 and fix it if it is affected.

What it is: CVE-2017-12573 is a high-severity command injection vulnerability in n/a, published on 24 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-12573 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-2017-12573/ (Markdown: https://insights.sbomify.com/CVE-2017-12573/index.md)
```

## Sources

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

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