# CVE-2020-25169: Reolink P2P Cameras

> Attackers can intercept sensitive camera feed data due to insufficient protection of data transferred between local devices and Reolink servers.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jan 2021
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-69qh-6j8v-ppx3

## What is CVE-2020-25169?

CVE-2020-25169 is a high-severity vulnerability in Reolink RLC-4XX series, published on 26 Jan 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The affected Reolink P2P products do not sufficiently protect data transferred between the local device and Reolink servers. This can allow an attacker to access sensitive information, such as camera feeds.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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

It affects 7 products.


Products: Reolink Rlc-410 Firmware, Reolink Rlc-422 Firmware, Reolink Rlc-423 Firmware, Reolink Rlc-423s Firmware, Reolink Rlc-510a Firmware, Reolink Rlc-520a Firmware, Reolink Rln8-410 Firmware.

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

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

## Is CVE-2020-25169 being exploited?

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

## Other vulnerabilities in Reolink RLC-4XX series

- [CVE-2020-25173](https://insights.sbomify.com/CVE-2020-25173/): Reolink P2P Cameras (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-25169 is a high-severity vulnerability in Reolink RLC-4XX series, published on 26 Jan 2021. 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-25169 in the wild and no public exploit code.

Affected product: Reolink RLC-4XX series. 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-25169/ (Markdown: https://insights.sbomify.com/CVE-2020-25169/index.md)
```

## Sources

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

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