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

> Attackers near the device's Wi-Fi can enable Telnet and gain root access using a hardcoded default password, compromising the Svakom Siime Eye camera.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Feb 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-w39f-xx4c-rgmv

## What is CVE-2020-11915?

CVE-2020-11915 is a medium-severity vulnerability in n/a, published on 8 Feb 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in Svakom Siime Eye 14.1.00000001.3.330.0.0.3.14. By sending a set_params.cgi?telnetd=1&save=1&reboot=1 request to the webserver, it is possible to enable the telnet interface on the device. The telnet interface can then be used to obtain access to the device with root privileges via a reecam4debug default password. This default telnet password is the same across all Siime Eye devices. In order for the attack to be exploited, an attacker must be physically close in order to connect to the device's Wi-Fi access point.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

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

It affects 1 product.


Products: Svakom Siime Eye Firmware.

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

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

## Is CVE-2020-11915 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-11920](https://insights.sbomify.com/CVE-2020-11920/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11915 is a medium-severity vulnerability in n/a, published on 8 Feb 2021. 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-2020-11915 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-11915/ (Markdown: https://insights.sbomify.com/CVE-2020-11915/index.md)
```

## Sources

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

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