# CVE-2016-10115: Hardcoded credentials in n/a

> Remote attackers can gain unauthorized access to NETGEAR Arlo devices using a default password after factory reset or in factory configuration.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 4 Jan 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-gg8c-3ww5-6v38

## What is CVE-2016-10115?

CVE-2016-10115 is a critical vulnerability in n/a, published on 4 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NETGEAR Arlo base stations with firmware 1.7.5_6178 and earlier, Arlo Q devices with firmware 1.8.0_5551 and earlier, and Arlo Q Plus devices with firmware 1.8.1_6094 and earlier have a default password of 12345678, which makes it easier for remote attackers to obtain access after a factory reset or in a factory configuration.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2016-10115?

It affects 3 products.


Products: Netgear Arlo Base Station Firmware, Netgear Arlo Q Camera Firmware, Netgear Arlo Q Plus Camera Firmware.

## How do I fix CVE-2016-10115?

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

## Is CVE-2016-10115 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-10116](https://insights.sbomify.com/CVE-2016-10116/): Weak cryptography in n/a (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10115 and fix it if it is affected.

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

## Sources

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

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