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

> Harmonic NSG 9000 devices use hardcoded default passwords for admin, guest, and config accounts, allowing unauthorized access.

- **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:** 5 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-wgxm-g76m-vmcr

## What is CVE-2018-14943?

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

### Official description

Harmonic NSG 9000 devices have a default password of nsgadmin for the admin account, a default password of nsgguest for the guest account, and a default password of nsgconfig for the config account.

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

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

It affects 1 product.


Products: Harmonicinc Nsg 9000 Firmware.

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

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

## Is CVE-2018-14943 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-14942](https://insights.sbomify.com/CVE-2018-14942/): Path traversal in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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