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

> Remote attackers can defeat cryptographic protections on Foscam devices by using a shared hardcoded SSL private key found in other installations.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/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:** 10 Apr 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-x9p4-3x2x-qpvx

## What is CVE-2017-7648?

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

### Official description

Foscam networked devices use the same hardcoded SSL private key across different customers' installations, which allows remote attackers to defeat cryptographic protection mechanisms by leveraging knowledge of this key from another installation.

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

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

It affects 12 products.


Products: Foscam C1, Foscam C1 Lite, Foscam C2, Foscam Fi9800xe, Foscam Fi9826p, Foscam Fi9828p, Foscam Fi9851p, Foscam Fi9853ep, Foscam Fi9901ep, Foscam Fi9903p, Foscam Fi9928p, Foscam R2.

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

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

## Is CVE-2017-7648 being exploited?

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

Public exploit code:

- A writeup of CVE-2017-7648 (github_poc): https://github.com/notmot/CVE-2017-7648.

## Fix prompt for AI coding agents

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

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

## Sources

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

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