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

> Attackers can execute arbitrary commands on NETGEAR ReadyNAS devices via command injection vulnerabilities.

- **Severity:** Medium 6.7 (`CVSS:3.0/AC:L/AV:L/A:H/C:H/I:H/PR:H/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Apr 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hrcg-cm8q-2p63

## What is CVE-2017-18854?

CVE-2017-18854 is a medium-severity command injection vulnerability in n/a, published on 29 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NETGEAR ReadyNAS 6.6.1 and earlier is affected by command injection.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


Products: Netgear Readynas Os Firmware.

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

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

## Is CVE-2017-18854 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-21102](https://insights.sbomify.com/CVE-2018-21102/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2017-18856](https://insights.sbomify.com/CVE-2017-18856/): Command injection in n/a (medium 6.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-18854 is a medium-severity command injection vulnerability in n/a, published on 29 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-18854 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-18854/ (Markdown: https://insights.sbomify.com/CVE-2017-18854/index.md)
```

## Sources

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

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