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

> Attackers can gain root access to WIFICAM devices via a hardcoded backdoor account accessible through TELNET.

- **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:** 25 Apr 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-r97g-5x4p-h964

## What is CVE-2017-8224?

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

### Official description

Wireless IP Camera (P2P) WIFICAM devices have a backdoor root account that can be accessed with TELNET.

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

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

It affects 1 product.


Products: Wificam Wireless Ip Camera \(P2p\) Firmware.

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

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

## Is CVE-2017-8224 being exploited?

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

Public exploit code:

- Wireless IP Camera (P2P) WIFICAM - Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-8225](https://insights.sbomify.com/CVE-2017-8225/): Auth bypass in n/a (critical 9.8)
- [CVE-2017-8221](https://insights.sbomify.com/CVE-2017-8221/): Information disclosure in n/a (high 7.5)
- [CVE-2017-8222](https://insights.sbomify.com/CVE-2017-8222/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2017-8223](https://insights.sbomify.com/CVE-2017-8223/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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