# CVE-2019-14919: Hardcoded credentials in n/a

> Hardcoded credentials in the Telnet service allow local attackers to gain root access and execute arbitrary code on the router.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mrmg-wq6p-w953

## What is CVE-2019-14919?

CVE-2019-14919 is a high-severity vulnerability in n/a, published on 9 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An exposed Telnet Service on the Billion Smart Energy Router SG600R2 with firmware v3.02.rc6 allows a local network attacker to authenticate via hardcoded credentials into a shell, gaining root execution privileges over the device.

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

## Which versions are affected by CVE-2019-14919?

It affects 1 product.


Products: Billion Sg600 R2 Firmware.

## How do I fix CVE-2019-14919?

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

## Is CVE-2019-14919 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-14920](https://insights.sbomify.com/CVE-2019-14920/): Command injection in n/a (high 8.8)
- [CVE-2019-14918](https://insights.sbomify.com/CVE-2019-14918/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-14919 and fix it if it is affected.

What it is: CVE-2019-14919 is a high-severity vulnerability in n/a, published on 9 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-14919 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-2019-14919/ (Markdown: https://insights.sbomify.com/CVE-2019-14919/index.md)
```

## Sources

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

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