# CVE-2020-26097: Hardcoded credentials in n/a

> Remote attackers can gain root access via telnet using embedded default credentials on unsupported PLANET NVR devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 18 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-g48h-whqf-89hj

## What is CVE-2020-26097?

CVE-2020-26097 is a critical vulnerability in n/a, published on 18 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The firmware of the PLANET Technology Corp NVR-915 and NVR-1615 before 2020-10-28 embeds default credentials for root access via telnet. By exposing telnet on the Internet, remote root access on the device is possible. NOTE: This vulnerability only affects products that are no longer supported by the maintainer

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

## Which versions are affected by CVE-2020-26097?

It affects 2 products.


Products: Planet Nvr-1615 Firmware, Planet Nvr-915 Firmware.

## How do I fix CVE-2020-26097?

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

## Is CVE-2020-26097 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-26097 and fix it if it is affected.

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

## Sources

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

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