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

> Attackers can use hardcoded passwords to enable SSH and gain root access, leading to remote code execution and full system takeover on PATLITE devices.

- **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 Mar 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2frq-p9c8-qr2h

## What is CVE-2018-18473?

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

### Official description

A hidden backdoor on PATLITE NH-FB Series devices with firmware version 1.45 or earlier, NH-FV Series devices with firmware version 1.10 or earlier, and NBM Series devices with firmware version 1.09 or earlier allow attackers to enable an SSH daemon via the "kankichi" or "kamiyo4" password to the _secret1.htm URI. Subsequently, the default password of root for the root account allows an attacker to conduct remote code execution and as a result take over the system.

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

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

It affects 3 products.


Products: Patlite Nbm-D88n Firmware, Patlite Nhl-3fb1 Firmware, Patlite Nhl-3fv1n Firmware.

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

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

## Is CVE-2018-18473 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-38625](https://insights.sbomify.com/CVE-2022-38625/): File upload in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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