# CVE-2017-18857: Hardcoded credentials in n/a

> The NETGEAR Insight mobile application mishandles passwords, potentially allowing attackers to compromise user accounts.

- **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:** 28 Apr 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-75r2-4c5g-c72f

## What is CVE-2017-18857?

CVE-2017-18857 is a critical vulnerability in n/a, published on 28 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The NETGEAR Insight application before 2.42 for Android and iOS is affected by password mismanagement.

Weakness: CWE-521 (Weak Password Requirements)

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

It affects 1 product.


Products: Netgear Insight.

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

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

## Is CVE-2017-18857 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-12591](https://insights.sbomify.com/CVE-2019-12591/): NETGEAR Insight Cloud with firmware before Insight 5.6 allows remote authenticated users to achieve command injection. (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-18857 is a critical vulnerability in n/a, published on 28 Apr 2020. 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-2017-18857 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-18857/ (Markdown: https://insights.sbomify.com/CVE-2017-18857/index.md)
```

## Sources

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

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