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

> Remote attackers can take full control of Rubetek cameras via Telnet due to a static, unchangeable high-privileged account password.

- **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:** 25 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-86hj-9869-w59w

## What is CVE-2020-25749?

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

### Official description

The Telnet service of Rubetek cameras RV-3406, RV-3409, and RV-3411 cameras (firmware versions v342, v339) could allow an remote attacker to take full control of the device with a high-privileged account. The vulnerability exists because a system account has a default and static password. The Telnet service cannot be disabled and this password cannot be changed via standard functionality.

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

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

It affects 3 products.


Products: Rubetek Rv-3406 Firmware, Rubetek Rv-3409 Firmware, Rubetek Rv-3411 Firmware.

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

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

## Is CVE-2020-25749 being exploited?

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

Public exploit code:

- CVE-2020-25749 (github_poc): https://github.com/jet-pentest/CVE-2020-25749

## Other vulnerabilities in n/a

- [CVE-2020-25747](https://insights.sbomify.com/CVE-2020-25747/): Missing authorization in n/a (critical 9.4)
- [CVE-2020-25748](https://insights.sbomify.com/CVE-2020-25748/): Information disclosure in n/a (high 8.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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