# CVE-2018-12668: Hardcoded credentials in n/a

> Attackers can access SV3C L-Series HD cameras using hard-coded credentials, potentially leading to unauthorized surveillance and control.

- **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:** 19 Oct 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-574h-r84q-h9rm

## What is CVE-2018-12668?

CVE-2018-12668 is a critical vulnerability in n/a, published on 19 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SV3C L-SERIES HD CAMERA V2.3.4.2103-S50-NTD-B20170508B and V2.3.4.2103-S50-NTD-B20170823B devices have a Hard-coded Password.

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

## Which versions are affected by CVE-2018-12668?

It affects 1 product.


Products: Sv3c H.264 Poe Ip Camera Firmware.

## How do I fix CVE-2018-12668?

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

## Is CVE-2018-12668 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-12666](https://insights.sbomify.com/CVE-2018-12666/): Auth bypass in n/a (critical 9.8)
- [CVE-2018-12667](https://insights.sbomify.com/CVE-2018-12667/): Auth bypass in n/a (critical 9.8)
- [CVE-2018-12670](https://insights.sbomify.com/CVE-2018-12670/): Command injection in n/a (critical 9.8)
- [CVE-2018-12671](https://insights.sbomify.com/CVE-2018-12671/): Information disclosure in n/a (critical 9.8)
- [CVE-2018-12669](https://insights.sbomify.com/CVE-2018-12669/): Missing authorization in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-12668 and fix it if it is affected.

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

## Sources

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

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