# CVE-2018-5399: Hardcoded credentials in DCU-210E

> Hardcoded SSH credentials in Auto-Maskin DCU 210E firmware allow attackers to gain root access and modify system files.

- **Severity:** Critical 9.4 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 8 Oct 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-qxxm-7g2q-pwxw

## What is CVE-2018-5399?

CVE-2018-5399 is a critical vulnerability in Auto-Maskin DCU-210E, published on 8 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Auto-Maskin DCU 210E firmware contains an undocumented Dropbear SSH server, v2015.55, configured to listen on Port 22 while the DCU is running. The Dropbear server is configured with a hard-coded user name and password combination of root / amroot. The server is configured to use password only authentication not cryptographic keys, however the firmware image contains an RSA host-key for the server. An attacker can exploit this vulnerability to gain root access to the Angstrom Linux operating system and modify any binaries or configuration files in the firmware. Affected releases are Auto-Maskin DCU-210E RP-210E: Versions prior to 3.7 on ARMv7.

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

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

It affects 2 products.


Products: Auto-Maskin Dcu-210e Firmware, Auto-Maskin Rp-210e Firmware.

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

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

## Is CVE-2018-5399 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-5399 is a critical vulnerability in Auto-Maskin DCU-210E, published on 8 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-5399 in the wild and no public exploit code.

Affected product: Auto-Maskin DCU-210E. 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-5399/ (Markdown: https://insights.sbomify.com/CVE-2018-5399/index.md)
```

## Sources

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

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