# CVE-2017-18819: Misconfiguration in n/a

> Incorrect security settings in NETGEAR ReadyNAS OS allow attackers to bypass security controls, requiring an OS upgrade to remediate.

- **Severity:** Medium 4.0 (`CVSS:3.0/AC:L/AV:L/A:N/C:L/I:N/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hhj2-6x24-45x4

## What is CVE-2017-18819?

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

### Official description

NETGEAR ReadyNAS OS 6 devices, running ReadyNAS OS versions prior to 6.8.0 are affected by incorrect configuration of security settings.

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

It affects 1 product.


Products: Netgear Readynas Os.

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

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

## Is CVE-2017-18819 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-21160](https://insights.sbomify.com/CVE-2018-21160/): Cross-site request forgery in n/a (high 8.0)
- [CVE-2017-18807](https://insights.sbomify.com/CVE-2017-18807/): Cross-site scripting in n/a (medium 5.2)
- [CVE-2017-18809](https://insights.sbomify.com/CVE-2017-18809/): Cross-site scripting in n/a (medium 5.2)
- [CVE-2017-18810](https://insights.sbomify.com/CVE-2017-18810/): Cross-site scripting in n/a (medium 5.2)
- [CVE-2017-18811](https://insights.sbomify.com/CVE-2017-18811/): Cross-site scripting in n/a (medium 5.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-18819 is a medium-severity vulnerability in n/a, published on 21 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-18819 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-18819/ (Markdown: https://insights.sbomify.com/CVE-2017-18819/index.md)
```

## Sources

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

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